Re:Ko – A concurrent, immutable, functional language
by steveklabnik on Thursday December 06, 2018 @08:32PM
(#18624361)
“let” us a required feature of the Rust grammar; the semantics would be significantly more complex without it, making tooling harder, etc. we didn’t add it for no reason.
[ Parent
| on HN ]
Re:Ko – A concurrent, immutable, functional language
by Ws32ok on Saturday December 08, 2018 @09:20AM
(#18635315)
Complexity often masks a lack of search for simplicity. Or was "let" the simplest answer?
Re:Ko – A concurrent, immutable, functional language
by steveklabnik on Saturday December 08, 2018 @11:23AM
(#18635929)
It's not a matter of "search for simplicity"; the grammar is just inherently ambiguous without some sort of token in this position. let was taken from OCaml, where a lot of inspiration from Rust came from.
(As a reader, it's also really nice to be able to see "there's a new variable being created here" at a glance. Ambiguity is a human problem as well as a computer problem.)