3 ms·
I understand many would love to have this yesterday but I strongly believe we should not speed it up. :) This is potentially the largest change the language wi
by josevalim 3y ago
I understand many would love to have this yesterday but I strongly believe we should not speed it up. :)
This is potentially the largest change the language will ever go through and we are being very intentional and deliberate on every step and decision we make. Once we start collecting feedback from the community, it may speed up or slow down the process, but I want to make sure everyone gets plenty of time to experience and internalize the changes.
When it comes to funding, the on-going work on Elixir type system is well funded by companies like Fresha, Starfish*, Supabase, and Dashbit. However, we also want to venture into new research areas, such as existential set-theoretic types, which would allow us to type behaviours (such as GenServer) similar to how one would type first-class modules in OCaml (or Typeclasses in Haskell). If someone is interested in sponsoring research work, hit me up (github.com/josevalim), and I can put you in touch with the proper institutions.
- moljac024 3y agoI would like to add that for what it's worth, I wouldn't mind slower compilation times if it means we get the type system as described. If it really does end up having a significant impact on performance, would you be open to making compile-time type-checking optional instead of scrapping the whole thing?
- josevalim 3y agoIf it comes to this, we will certainly need to have a discussion on the topic. So I am definitely open to discussing the idea!