https://linen.dev logo
Join Discord
Powered by
# react
  • g
    Ah cool, that makes sense
  • u
    e.g. I think there is a react c# somewhere in the ether. I'm not sure if it would give you any benefits to server side connection, I imagine it would be exactly the same.
  • c
    that basically boils down to a language comparison, ts/js vs haxe
  • c
    and my answer is: abstracts & macros
  • g
    I haven't yet found a decent use case for abstracts apart from naming enums 🤷‍♂️
  • b
    Main use for abstracts for me is being able to write safer and more descriptive code without sacrificing performance.
  • g
    @User have you got an example/use case of how an abstract achieves this?
  • b
  • b
    Various wrappers that limit/change the API.
  • b
    Operator overloading (though that's not generally what abstract types are about – just happens to be the way to implement it in Haxe).
  • b
  • a
    @User For material-ui lib 
    theme.spacing()
    is meant to have 4 parameters but your lib only has 1 is there a different API I should use to simulate the full effect?
  • u
    Seems like an oversight, PRs welcome to support more arguments
  • a
    coolio!
  • a
    wait, how is a typedef a function call xD
  • a
    I was gonna do a 
    @:overload
    but the function is defined as 
    @:optional var spacing:Float->Float;
    in a typedef
  • a
    that's a neat trick?
  • a
    I guess, just change it to 
    Float->Float->Float->Float->Float
    ?
  • a
    Nevermind, got a neater way to do it 👍
  • u
    Yeah, the `Float`s (with 
    ?
    !) could do
  • a
    Nah, even neater and no 
    null
    :D
  • a
    Rest
  • u
    Meh
  • u
    Rest has no notion of "up to 4 float arguments"
  • a
    It doesn't, but it works appropriately
  • a
    I think it's the closest to the standard api
  • a
    and going passed the 4th parameter it just doesn't do anything
  • a
    I think most people get the css style api of the 4 params tho
  • u
    Float->?Float->?Float->?Float->Float
    is the closest (the correct), not 
    Rest<Float>
  • a
    rip, sent the pr x_x
1...484950...80Latest