I was excited to see the introduction to modern Haskell as I find that it's very confusing to enter Haskell these days as many or most introductions doesn't actually match current practices (Text vs. String, cabal vs. plain GHC, etc). However, I was bewildered when the Cabal & Stack section didn't mention Stack. Is this merely waiting for someone to write it? At the very least, we should be

I think it ought to be possible to speed up https://github.com/gallais/agdarsec quite a lot
by not converting a String (aka Haskell's Text) to a List Char but rather processing
the string immediately.

To be able to do that & have the parsers still run at compile time, I need:

• Maybe as a builtin
• uncons : Text -> Maybe (Char, Text) as a primitive
• `length-uncons

I think a good rule of thumb would be that if you can't imagine making practical use of file B without file A, then B should export A. For instance, Modality exports ReflectiveSubuniverse because so many of the theorems about modalities are actually theorems about reflective subuniverses. It's hard to imagine talking about colimits without needing to talk about diagrams too, so I agr

At the moment our issues are a mess, and not very well categorised. We should probably adopt a labelling scheme like Rust's!

Plasma has a nice labelling scheme with a 'skill' label. This might help folks find something that they can help out with!

input:

(name bool (mu (true 1) (false 1)))

output:

encodeBool :: Serialiser Bool
encodeBool true = word8 (fromIntegral 0)
encodeBool false = word8 (fromIntegral 1)

expected:

encodeBool :: Serialiser Bool
encodeBool True = word8 (fromIntegral 0)
encodeBool False = word8 (fromIntegral 1)

Right now, this is a hodge-podge of useful functions, but it is hard to understand how to use them except by looking at examples. It would be helpful to close this up under a signature, which could later be even documented...

I think it would be cool to write

Cx.ext_dim blah... @@ fun x ->
Cx.ext_ty foo... @@ fun y ->
Cx.def hey... @@
cx

It will be interesting to implement trees, codata, etc

• Bitbucket: https://bitbucket.org/lambdamix/superspec/issue/27
• Originally Reported By: Ilya Klyuchnikov
• Originally Created At: 2013-08-28T09:02:42.726

I figured out that that function addresses are not always preserved at runtime when built in release mode.