jordan
bytestring
Our great sponsors
jordan | bytestring | |
---|---|---|
3 | 15 | |
27 | 283 | |
- | 1.1% | |
0.0 | 7.9 | |
almost 2 years ago | 13 days ago | |
Haskell | Haskell | |
- | 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.
jordan
-
Monthly Hask Anything (July 2022)
I'm having some trouble getting GHC to use a quantified constraint in my library jordan (Link is to the specific PR where the issue is arising, and is very much a WIP).
-
Writing about Haskell is Hard
> Let’s say I wanted to introduce Jordan at work, as part of a drive for a Haskell web service. I’d have to explain to everybody what the hell Rank-N types are
If so, that's a problem of jordan's documentation. If it's documented with enough practical examples of how to get things done, and it's not buggy, no one needs to know about how it does it, or even why we have to write "forall" here. And I see from the article that it even uses generic so you can get instances derived for you (probably don't even have to add the RankNTypes pragma in your own files). Even the hand-written examples of https://github.com/AnthonySuper/jordan/blob/master/jordan/RE... don't seem to require any esoteric knowledge. But it's probably hard to write about Haskell without showing off all the fancy features that make things work under the hood :)
I remember following http://www.serpentine.com/wreq/tutorial.html years ago for work while starting out with Haskell. It introduced the absolute minimal stuff needed for lens (I didn't delve any deeper into lens than what the tutorial showed), and I was immediately productive. Now I took a quick look at the source of wreq and the first file I see has RankNTypes, GADT's, etc. and I never knew.
-
[ANN] Jordan: Abstract, inspectable JSON Serialization and Parsing
The github page for this project is located here. While I'm not gunning to replace Aeson or anything, I would really appreciate any feedback anybody has to offer!
bytestring
-
RunWithScissors() (2009)
The documentation is itself fairly funny, for those who don’t care to click ahead:
> This "function" has a superficial similarity to ‘unsafePerformIO’ but it is in fact a malevolent agent of chaos. It unpicks the seams of reality (and the IO monad) so that the normal rules no longer apply. It lulls you into thinking it is reasonable, but when you are not looking it stabs you in the back and aliases all of your mutable buffers. The carcass of many a seasoned Haskell programmer lie strewn at its feet.
> Witness the trail of destruction:
https://github.com/haskell/bytestring/commit/71c4b438c675aa360c79d79acc9a491e7bbc26e7
-
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).
- Some light investigation regarding ByteString's IsString instance, and its conclusions
-
Haskell - Important Libraries
bytestring
-
[ANNOUNCE] GHC 9.2.2 is now available!
Note that this release is broken for Windows.
-
Beginner level tutorial - bytestring
I've opened https://github.com/haskell/bytestring/issues/455 so the situation can be improved. You're very welcome to chime in on the discussion or to contribute some of the missing documentation yourself! :)
-
bytestring-0.11.2.0
Highlights from the changelog:
- [Haskell]
-
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.
What are some alternatives?
learnyouahaskell.github.io - A community version of the renowned "Learn You a Haskell" (LYAH) tutorials collection!
bytestring-read - fast ByteString to number converting library
autodocodec - self(auto)- documenting encoders and decoders
bytestring-typenats - Haskell ByteStrings annotated with type-level naturals for lengths
dependent-sum - Dependent sums and supporting typeclasses for comparing and displaying them
bytestring-builder - The new bytestring builder, packaged outside of GHC
monad-bayes - A library for probabilistic programming in Haskell.
bytestring-tree-builder - A very efficient ByteString builder implementation based on the binary tree
obelisk - Functional reactive web and mobile applications, with batteries included.
bytestring-delta - Simple binary diff/patch library for C and Haskell
bytestring-plain - Plain byte strings (`ForeignPtr`-less `ByteString`s)
streamly-bytestring