rio-orphans
ifcxt
| rio-orphans | ifcxt | |
|---|---|---|
| 6 | 4 | |
| 853 | 116 | |
| 0.6% | 4.3% | |
| 2.1 | 0.0 | |
| 9 months ago | over 7 years ago | |
| Haskell | Haskell | |
| MIT 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.
rio-orphans
-
Haskell IHP Framework, from a Technical and Business Perspective
https://github.com/commercialhaskell/rio#language-extensions which is cited as an example in simplehaskell's page on recommendations.
- [ANN] text-display 0.0.1.0: A typeclass for user-facing output
-
Haskell: The Bad Parts, part 2 (2020)
> Can we move to a better standard lib? Here Snoyman has put forward a great effort by releasing his classy-prelude, but iirc he also stopped using it.
He mentioned https://github.com/commercialhaskell/rio in the 1st article, it's interesting, I wasn't aware of it. (I am using classy-prelude but I might try it out.)
-
Are similar effects system like in Scalas ex: Cats Effects, ZIO etc also available in Haskell?
rio
-
Why exactly I want Boring Haskell to happen
It's worth mentioning that Snoyman's "Boring Haskell" is actually a fairly moderate position: if you look at his suggested list of language extensions, it's pretty broad (and fairly reasonable in my view).
-
Haskell The Bad Parts Part 1
via ByteString was recommended by Snoyman in the post Beware of readFile (referenced in the Haskell: The Bad Parts, part 1 too). But this has got a disadvantage compared to Data.Text.IO combined with hSetEncoding. This might be a good time to update Beware of readFile, u/snoyberg.
ifcxt
-
Monthly Hask Anything (August 2022)
Even the IfCtx "tricks" and stuff like /u/Noughtmare's post don't resolve the constraints at runtime. The constraints are still resolved statically, you just carry around a (constant) token that indicates how compile-time resolution went.
- Different `Num` instances based on availability of another instance.
- How do I define this super-unsafe type class (not internally consistent at all 😱)
What are some alternatives?
basic-prelude - An enhanced core prelude, meant for building up more complete preludes on top of.
auto - Haskell DSL and platform providing denotational, compositional api for discrete-step, locally stateful, interactive programs, games & automations. http://hackage.haskell.org/package/auto
time-warp
safe-exceptions - Safe, consistent, and easy exception handling
ghc-proposals - Proposed compiler and language changes for GHC and GHC/Haskell
transient-universe - A Cloud monad based on transient for the creation of Web and reactive distributed applications that are fully composable, where Web browsers are first class nodes in the cloud