Our great sponsors
-
bytestring
An efficient compact, immutable byte string type (both strict and lazy) suitable for binary or 8-bit character data.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
elm-format
elm-format formats Elm source code according to a standard set of rules based on the official Elm Style Guide
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
via commonmark-pandoc typeclass instances.
I'm trying to iron out API discrepancies between flavours of ByteString in https://github.com/haskell/bytestring/issues/289, any help would be much appreciated.
I use haskell-mode. It has a shortcut for loading a module into REPL, and it also runs hasktags for me. That's literally all I use.
Take for example the debate about 2 vs 4 spaces. People often (but not always) have very strong opinions about this, yet it is clear that this formatting choice will probably not be the dominant factor in the success of a project. A quick google search also reveals no scientific research in this field. Concerning surveys, I found this interesting (from a survey on 2 vs 4 spaces in elm-format) as one datapoint: