Hacker News Reader

Comment by bhaney | Hacker News Reader

I'm excited about the type system so far, but I'm especially excited to hear about what else the type system is going to enable in the future. I remember José describing this as a "gradual gradual type system," where the gradual type system is going to be gradually added in stages, with this being the first stage. Any cool new type-system-related stuff coming up in the next few stages? I'm especially hoping for newly enabled compiler optimizations.

View on HN

Here is the roadmap https://hexdocs.pm/elixir/main/gradual-set-theoretic-types.h...

The next milestone will include a mechanism for defining typed structs.

Doesn't gradual type system mean something else here? As in developers being able to iteratively add types while leaving untyped parts for later? At least this is how Ruby's Sorbet describes it

Yes, but the discussion here was about it being a gradual, gradual type system, as in, the gradual type system being added gradually

You’re right about what a gradual type system means! A gradual type system allows flexibility in how you approach typing a codebase. It also means that your system incorporates a dynamic type, making your types 'gradual'.

Interestingly, gradual set-theoretic types are flexible enough to let you gradually implement type inference for that system. Hence, the gradual gradual type system. :-)

Correct, a gradual type system is a form of type system and not the method for rolling it out.

It's a gradual type system that they're rolling out gradually.

Reply on news.ycombinator.com