why do ML programmers put up with this endless sea of ".t".
Conversation
twitter.com/glaebhoerl/sta
(if you know of a nice way to resolve this I am very interested)
Quote Tweet
1. conflating types with modules is Wrong
2. ML's `Foo.t` idiom is unsightly
3. Haskell's `import Data.Map.Map` idiom is unsightly
me: 
1
2
(which two syntaxes do you mean? . and ::?)
Rust does conflate types and modules, aka `impl` blocks and "UFCS"
1
1
It's kiiind of neat from an ergonomics perspective. Less names to come up with. Lean is interesting - each type adds a new namespace that you can add stuff to. Not sure how it works out though. Personally I prefer just going with modules==records though.
3
'works out' in the sense of 'what the theory looks like'.