https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b

    bright-gpu-74537

    08/31/2022, 8:56 AM
    thats fine with me 😅
  • p

    powerful-morning-89

    08/31/2022, 8:58 AM
    Just need to get all the libraries to move to
    Run.hx
    and move haxelib away from Neko. Fun fact: the haxelib server still requires Haxe 3
  • b

    big-angle-82801

    08/31/2022, 8:59 AM
    We need a better option than Run.hx, there is a very noticeable compilation delay when moving a library from neko to eval (not to mention that haxe compiler updates might break compilation and prevent people just trying to run the library script)
  • b

    best-agent-85158

    08/31/2022, 9:00 AM
    *Not so fun fact
  • p

    powerful-morning-89

    08/31/2022, 9:03 AM
    run.hl
    then. > haxe compiler updates might break compilation and prevent people just trying to run the library script If the run script breaks chances are the library itself is broken too, so...
  • b

    big-angle-82801

    08/31/2022, 9:04 AM
    yes, but some libs are mostly about the script, like haxelib itself, or things like hlc-compiler which broke bc of all those abstract transitivity changes
  • b

    big-angle-82801

    08/31/2022, 9:07 AM
    tbh tho it wouldn't be too hard to get it to use run.hl, the main problem would probably be that right now there isn't a good way of installing hashlink on most systems apart from building from source
  • b

    big-angle-82801

    08/31/2022, 9:07 AM
    but still we shouldn't leave neko broken ;)
  • p

    powerful-morning-89

    08/31/2022, 9:08 AM
    Indeed, we should delete it :)
  • b

    big-angle-82801

    08/31/2022, 9:13 AM
    have you tried
    -v
    ? or does it happen when compiling the neko byte code?
  • b

    bright-gpu-74537

    08/31/2022, 9:14 AM
    i havent really tried anything tbh, just
    lime test neko
  • p

    powerful-morning-89

    08/31/2022, 9:15 AM
    Happens deep in the bowels of the neko generator, so
    --verbose
    doesn't help. See
  • b

    big-angle-82801

    08/31/2022, 9:17 AM
    ah yh that makes sense
  • b

    big-angle-82801

    08/31/2022, 9:19 AM
    is that the neko generator or the neko compiler?
  • p

    powerful-morning-89

    08/31/2022, 9:19 AM
    The thing that actually outputs the final bytecode I think. So compiler, I guess?
  • b

    big-angle-82801

    08/31/2022, 9:20 AM
    is there a no compile option for neko? 🤔
  • p

    powerful-morning-89

    08/31/2022, 9:21 AM
    -D neko-source
    but that seems to give a stack overflow too iirc. And a`-D use-nekoc` but that throws an error in, I assume, nekoc.
  • b

    big-angle-82801

    08/31/2022, 9:22 AM
    that's odd
  • p

    powerful-morning-89

    08/31/2022, 9:22 AM
    -D neko-source
    => stack overflow
    -D use-nekoc
    => stack overflow in nekoc
  • b

    big-angle-82801

    08/31/2022, 9:22 AM
    but at least the behaviour is consistent between haxe's built in neko compiler and nekoc
  • b

    big-angle-82801

    08/31/2022, 9:24 AM
    wow
  • b

    big-angle-82801

    08/31/2022, 9:25 AM
    i guess we're only on neko 2
  • p

    powerful-morning-89

    08/31/2022, 9:25 AM
    neko_v1
    errors with
    /home/zeta/.local/share/haxelib/openfl/9,1,0/src/openfl/display/DisplayObjectContainer.hx:516: characters 68-78 : This integer is too big to be compiled to a Neko 31-bit integer. Please use a Float instead
  • b

    big-angle-82801

    08/31/2022, 9:25 AM
    31 bit 😅
  • b

    big-angle-82801

    08/31/2022, 9:26 AM
    i would imagine that's not related to the current error?
  • b

    best-agent-85158

    08/31/2022, 9:26 AM
    openfl compiles fine to neko 🤔
  • b

    best-agent-85158

    08/31/2022, 9:26 AM
    at least on latest
  • p

    powerful-morning-89

    08/31/2022, 9:26 AM
    Does your project include haxeui?
  • b

    best-agent-85158

    08/31/2022, 9:26 AM
    yes
  • b

    big-angle-82801

    08/31/2022, 9:26 AM
    has an issue been created yet?
1...123512361237...1687Latest