What do you think is important to know in order to write good Haskell code? I am referring to both theoretical topics and good programming practices that you think are important. What do you wish you had known when you learned Haskell? All answers are welcome

A list of assorted suggestions: Use Text (strict) or ByteString (strict) instead of String. Use foldl' when your producing accumulator function is strict. Don’t jump to fancy language extensions. Learn how to design programs with simple tools like HOFs, ADTs, Functional Core / Imperative shell. Us…

[image] ChShersh: Choose a formatter and use it. fourmolu or ormolu are great choices. I have been only using stylish-haskell. Are they very different?

Writing good Haskell code is not very different from writing good code in other languages. It’s always a matter of proper engineering and knowing best practices. Good code is a consequence of a good design and architecture. Simplicity. The code should be as simple as possible, but not simpler. Acc…

[image] graninas: Writing good Haskell code is not very different from writing good code in other languages. I strongly agree and think this is one of the key messages the Haskell community should be pushing. It would demystify Haskell to outsiders and help improve the quality of software wri…

Might you or others be interested in posting a framework guide? Playing around with Monomer and Servant, it’s obvious why you might want a framework; it gets that pesky IO code out of the way (and also allows you to dodge program-structuring wars) and lets you play more with pure functions. I’m act…

[image] maxigit: But avoid type synonym. They add a layer of indirection and make error message more confusing. I find them useful for documentation purposes, Title -> Category -> Author -> Post is better than String -> String -> String -> Post.

In my book, there is an introduction to Servant. However, having a separate tutorial would be nice. I and my team have designed EulerHS for Juspay in order to simplify the backend development, including SQL, KV DB, logging etc. (SQL is not extremely simple though because it uses beam). In essence, …

Build types such that wrong states do not have a representation Don’t try to find the most elegant/abstract solution right away, but go for simplicity at first Once stuff kind of works, never hesitate to do a big refactoring Those hints take advantage of the fact that the compiler can be your frie…

what are Haskell’s notions of functional interfaces?

I like stylish haskell a lot. Fourmolu and I had to split up, it didn’t work out between us.

Haskell Community

Important things to know about writing good haskell code

Learn

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled