4 ms·
I don't think it's Lisp envy. They're porting stuff from F#, which as far as I know is from the ML family.
by oblio 8y ago
I don't think it's Lisp envy. They're porting stuff from F#, which as far as I know is from the ML family.
- noblethrasher 8y agoWell, to be clear, I was being tongue-in-cheek when calling it "envy". I just mean that C# looks messy from the point-of-view of an ML-wannabe, but pretty elegant as an aspiring Lisp. And I say this as someone that is fluent in F# and prefers functional programming in the style of ML rather than that of Lisp.
- falcrist 8y agoThis change was definitely inspired by F# (or ML ultimately). It's far from the first feature to be brought over. Look at async/await, usable tuples, lambda functions, range syntax, etc.
- moomin 8y agoAFAICT, this is kind of true for a lot of F#: F# is where they do the experimentation, C# is where they do the more heavily engineered "fast" version.
- falcrist 8y agoThat seems to be true at least to some extent. However, there are some noteworthy parts of the two languages that seem to be intentionally different. For example, F# optimizes tail recursion while C# doesn't.
- deleted 8y ago[deleted]
- pjmlp 8y agoLINQ actually came from Haskell. "Confessions of a Used Programming Language Salesman, Getting the Masses Hooked on Haskell" http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.72.868&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.72....