I’d say, read Hyprland’s responses linked elsewhere in this thread before making any hasty decisions.
It seems (but I’m not sure, to be clear), that it was a situation that got solved, and people are still hung up on it.
It’s like that “but you fuck one sheep” joke.
I thought of Pascal, Java and C#, but pretty much any language listed here as “explicit / nominal / static” makes the cut:
https://en.wikipedia.org/wiki/Comparison_of_programming_languages_by_type_system
Oh, so what you’re describing is strong typing. I thought it was a unique feature of Ocaml. But in reality, any strong-typed language will have this as well.
And yeah, Typescript merely “suggests” typing, and it will allow you to build the project even if you ignore the type errors. A build system refusing to, well, build, if there are typing errors usually takes care of this, but again, the dev team may as well not implement this.
What’s so special about Ocaml’s type system?
A PR fixing all those issues was merged.
They used “they” when referring to a person, and “it” when referring to a process (the author used “he” when referring to a process calling another process, when he should have used “it.”)