elm-format
bytestring
Our great sponsors
elm-format | bytestring | |
---|---|---|
5 | 15 | |
1,306 | 282 | |
- | 0.7% | |
5.6 | 7.9 | |
about 1 year ago | 7 days ago | |
Haskell | Haskell | |
BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
elm-format
-
Elm 2021, a year in review
9ᵗʰ - Aaron VonderHaar releases a new version of elm-format.
-
Setting up an Elm project in 2022
Unlike Javascript, Elm has an official Style Guide for how Elm code should be structured. In addition, some formatting is built into the language itself, such as requiring indents of four spaces. This removes a major point of contention within teams. In addition, the community has put together a wonderful tool called elm-format. Similar to Prettier, this utility can be used to ensure that all Elm code matches the official style guide. Unlike Prettier, there is no custom configuration, meaning once again that your team can focus on writing code instead of what kind of quotes to use.
-
Tips/Resources on starting with ELM
Regarding user experience and tooling, I'd suggest you use an editor that is compatible with the elm language server: https://github.com/elm-tooling/elm-language-server VSCode is a good default choice. You'll also be interested in other toolings. elm-json (https://github.com/zwilias/elm-json) is great to simply install and uninstall dependencies. elm-format (https://github.com/avh4/elm-format) is a must since most active people in the community use it, and simply viewing your code being moved around on save is a good sign that you wrote something with a good syntax.
-
Artyom's Haskell toolbox — a long list of tools/libraries 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:
bytestring
-
Monthly Hask Anything (July 2022)
If you bring in efficient strings from bytestring, densely packed arrays from vector, and an in-place sort from vector-algorithms, you can bring it down to 275ms (uses 19MB of mem).
-
Haskell - Important Libraries
bytestring
-
[ANNOUNCE] GHC 9.2.2 is now available!
Note that this release is broken for Windows.
-
Dragging Haskell Kicking and Screaming into the Century of the Fruitbat :: Reasonably Polymorphic
Well, ByteString in particular should not have an IsString instance in a new report. That's pretty clear by https://github.com/haskell/bytestring/issues/140 : the concensus is that there is no good solution right now, but it should not have gotten an IsString instance in the first place. If a theoretical new Haskell Report 202x includes OverloadedStrings (as it should) to handle string literals analogously to numeric literals, I'd expect it to not give ByteString (which is really just a collection of octets) an IsString instance, with all it's issues and rattail due to the encoding question being implicitized.
-
How can Haskell programmers tolerate Space Leaks?
Standard streaming libraries. They are being written by people that make the effort to understand performance and I have a hope that they make sure their streams run in linear space under any optimizations. It is curious and unsettling that we have standard lazy text and byte streams at the same time — and the default lazy lists, of course. I have been doing some work on byte streams and what I found out is that there is no way to check that your folds are actually space constant even if the value in question is a primitive, like say a byte — thunks may explode and then collapse over the run time of a single computation, defying any effort at inspection.
-
NorfairKing/haskell-dangerous-functions ; Call for contributions
Apparently it's not very optimized though, as you pointed out yourself: https://github.com/haskell/bytestring/pull/371#issuecomment-786967047
-
Haskell ghost knowledge; difficult to access, not written down
If you need fast Double rendering you can get a significant improvement by using double-conversion or the Ryu branch of bytestring. Again, you'd expect that "how to show a floating-point number quickly" would be a solved problem, but it's not.
-
GHC 2021!
OverloadedStrings has a bad ByteString instance and should indeed be avoided: https://github.com/haskell/bytestring/issues/140
-
Artyom's Haskell toolbox — a long list of tools/libraries I use
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.
What are some alternatives?
bytestring-read - fast ByteString to number converting library
bytestring-typenats - Haskell ByteStrings annotated with type-level naturals for lengths
bytestring-builder - The new bytestring builder, packaged outside of GHC
bytestring-tree-builder - A very efficient ByteString builder implementation based on the binary tree
bytestring-plain - Plain byte strings (`ForeignPtr`-less `ByteString`s)
streamly-bytestring
bytestring-delta - Simple binary diff/patch library for C and Haskell
elm-review - Analyzes Elm projects, to help find mistakes before your users find them.
bsparse - bytestring parser
bytestring-arbitrary - Arbitrary instances for ByteString
elm-ui - What if you never had to write CSS again?
pathological-bytestrings - Facilities for testing with ByteStrings