Post by Markel Kaj on May 1, 2018 22:36:10 GMT
I didn't come to the forum for nothing. As much as I am impressed with the stated features and goals of lux, the one thing is missed out of the feature list that I am particularly concerned with is what's lux's take on null/nil/none/nan-safety? Yeah, not the concurrency model but that thing. I don't know why but nulls drive me insane. I know, some languages have it (clojure, go, python) but the pain is somewhat mitigated by certain conventions dictated by the user community of the language and language itself to the degree. Statically typed languages and particularly new ones have super nifty feature to handle nulls (Kotlin, Swift, Ceylon?): nullable types, others claim they don't have nulls at all (Julia, Pony, certain Beam-languages as Erlang?). I know, functional statically-typed languages do not usually suffer from the null problem: scala has option type (but it had or even still has an overhead), haskell has maybe (but it also has "Nothing" that came from god knows where in the past, don't know how it is now). What does Lux have? Since we are speaking about functional languages. Is Lux by chance pure in the sense haskell is? It will be very interesting if it is since lisps usually are not 
, but they aren't usually statically typed either XD, so it wouldn't be that surprising.
Regards,
, but they aren't usually statically typed either XD, so it wouldn't be that surprising.Regards,
? Or it isn't the time to ask such rhetoric questions yet because the time machine is not at your disposal? Jokes aside, thanks for the answer. I still have a few questions but it will be better to create separate threads for them and I will ask the questions a bit later just not to be annoying.