https://linen.dev logo
Join Discord
Powered by
# lime
  • b
    i am not sure how i can do it better at now there (really complex for sure there with macros and abstracts and all of @structInit on top ... hm)
  • b
    so if all haxe-language-spice will be mixed together
  • b
    i feel same like into 
    perl[2-4]-times
    sometimes into ;:)
  • a
    haha
  • a
    yeah I am still somewhat trying to avoid the more complex haxe stuff
  • a
    I want to easily read and edit the code
  • r
    @structInit isnt super complex at all
  • a
    and macros seems like a whole layer of obfuscation I just haven't had the heart to entertain
  • b
    ( *`real`-> independend from hardware and driver i mean .)
  • r
    just make all fields you need for initialization public and then treat it like a typedef
  • a
    you don't even need to have public
  • a
    at init stage
  • b
    ever did macros into C or GLSL ?
  • r
    personally when my fields werent public structInit didnt work properly
  • a
    never
  • b
    haxe is much much better into macros
  • r
    macros are something to say the least
  • r
    im sure theyre super satisfying to work with (once the compiler doesnt scream at you to have your args be expressions), but i dont really have any use case for them sadly
  • b
    at the end all is only something like -> pre-processing
  • b
    (or the pre-renderpass 😂 -like ;:)
  • b
    YanniZ06 and do you really need that -> 
    autocomplete
    ?
  • b
    to be fast into coding i mean ?
  • r
    huh
  • r
    wdym
  • a
    nobody needs it
  • a
    but it's damned useful
  • r
    autocomplete is way too slow on my vsc anyways lmao
  • b
    sry.. half and me talked about before
  • r
    by the time autocomplete shows up for me days have passed
  • a
    yeah it's only useful when you are exploring an API, when you're actually writing code it's quicker to just type it
1...125126127...138Latest