In Haskell I just write the definitions without regard if/when/how often/how many times they will be used. And ultimately, if people find it doesn't make the right sorts of trade-offs for them, they can and should use GHCJS or Haste, but there are plenty of use cases where it is a good fit.Įxactly. I think we're making good progress, but the end goal was never parity with GHC. Generally, please remember that PS doesn't have the benefit of 20 years of research behind it. If you try to use PureScript like Haskell without regard for the differences in evaluation order then you're going to have a bad time. Well yes, it's strict for different reasons. What would your ideal record system look like? In general records are not pleasant to work with at all. You can derive Newtype instances or use lenses.
In Haskell you can write newtype Foo = Foo and you get the unFoo function for free.
HASKELL LANGUAGE CODE
Others have used code generation to get around any boilerplate issues. Well psc doesn't do much in the way of optimization yet, but I'm hoping to focus on that after 1.0. Generics is not an option because it produces horribly slow code. While GHC is constantly moving forward with new language features, the whole Haskell ecosystem appears more focused on solving practical issues than the PS ecosystem. Reasons are: multiple levels of abstraction (polymorphic functions add overhead), all functions are curried even if fully applied (gives runtime no chance to optimize the functions, and produces a lot of garbage). It's easy to write innocently looking code which performs glacially slow at runtime. Have to constantly check the generated code and rewrite if necessary.
What I see though is me having problems with my wrists because I write thousands of lines of code each day.Īlso, PS is strict, which makes certain things which would be relatively easy to do in Haskell a lot more difficult.Īnd I worry a lot more about performance. The developers justify it by the increased type safety. But PS makes you write soooo much (boilerplate) code. I love the type safety (I worked with Haskell a few years ago and I do like statically typed languages). Ask a question on Haskell Stack Overflow.This includes a human posting the output of a bot, such as ChatGPT.īlockchain posts must be tagged Blockchain posts are allowed as long as they are related to Haskell, but they must use the "blockchain" tag. They will be banned with extreme prejudice. Bots cannot be used to make posts or comments. Simply looking for people with interest in or experience with Haskell is not sufficient. Job postings are allowed as long as the job actually involves working with Haskell. Questions about homework are fine, but this subreddit is not here to do your homework for you. Both asking and answering homework questions is not allowed. No matter how funny, memes and image macros are not allowed. Posts about topics that are adjacent to Haskell, like for example functional programming, are typically allowed. For example a post about OCaml would only be allowed if there was a connection to Haskell. Top-level posts should be primarily about Haskell. The Haskell programming language community.ĭaily news and info about all things Haskell related: practical stuff, theory, types, libraries, jobs, patches, releases, events and conferences and more.
0 kommentar(er)
