Re:Comparing the Same Project in Rust, Haskell, C++, Python,...
by garmaine on Sunday June 16, 2019 @12:27AM
(#20193836)
That was where I stopped reading. If a library like lens—used by nearly every haskeller in every project—was disallowed, I don’t know what the purpose of this exercise was.
Re:Comparing the Same Project in Rust, Haskell, C++, Python,...
by pyrale on Sunday June 16, 2019 @02:23PM
(#20197044)
Lens is far from being used by everyone in the space. On a sample of 5-6 professional users I talked with at this zurihac, most didn't use it.
Re:Comparing the Same Project in Rust, Haskell, C++, Python,...
by aliceryhl on Sunday June 16, 2019 @05:01AM
(#20194598)
I mean, it seems like it was an university course, and writing a compiler from scratch is probably a decent exercise in a compiler course.
Re:Comparing the Same Project in Rust, Haskell, C++, Python,...
by garmaine on Sunday June 16, 2019 @05:47AM
(#20194709)
Restrict the students from using a parser library. I get that. But allowing nothing except that standard library? That’s stupid.
It also makes the language comparison useless. Python has a standard library that is continuously improved and people reach to that when writing programs. Haskell, like C, ossified it’s standard library when it was created and people use the external packages for equivalent up to date libraries.
Re:Comparing the Same Project in Rust, Haskell, C++, Python,...
by Ericson2314 on Sunday June 16, 2019 @05:44PM
(#20198094)
Parsers are not the interesting parts of compilers.
Re:Comparing the Same Project in Rust, Haskell, C++, Python,...
by tathougies on Sunday June 16, 2019 @12:17PM
(#20196230)
I dunno, libraries like earley in Haskell, provide pretty nice error messages.
More anecdotally, I’d argue parsing libraries are common, just look at the prevalence of attoparsec and others. But most parsing libraries in the ecosystem are parser combinator libraries which don’t support as performance and nice error messages that compilers need