You asked for an example and I provided the closest example that exists for BEAM languages where type inferencing is strictly better than static type declarations.
@dimitarvp You’re arguing on an unfair basis and purposely missing the point.
Gleam uses type inferences to obtain strong typing which is the point I am trying to make as something similar to but not identical to what I am describing (as I also want value constraint checking).
In Gleam, type annotations or declarations are not required, the types are not static in the sense they don’t have to be statically declared by the developer and even if used, they don’t actually influence the type inferencing whatsoever, the compiler knows despite what decorations you use. The code is therefore amenable to a change in types without refactoring because it’s not an echo chamber of repeat yourself static type declarations on everything.
It is telling that you have expressed numerous times that you live in a land of refactoring hell and your reaction was one of incredulousness that refactoring was not of any consequence to me within my development.
Understand that brittleness actually emerges from static type declarations and it begets more code and a lot more code churn. Add throws onto things, async and all the type ceremony that inferior languages do and sure, life is a refactoring nightmare. I avoid these tarpits and I don’t want Elixir sliding down this slippery slope into the tar either.
I don’t think I have said it enough, as clearly it did not get through:
I do not want to be reminding the compiler what the type or value constraint is all over my code, I want strong typing and value constraint inferencing without the developer overhead or effort of manually maintained static types.
You disagree with the above it seems.
I simply want more checking than you, for much less effort and I do not want the Elixir language being ruined through well intentioned but brittle static type declarations which you seem to think is the only way.
Elixir typespecs and specs are already an eyesore and overhead that I cannot wait to be rid of with type inferencing.
