Peter Trško

I just found myself writing: ```Dhall λ(t : Type) → λ(v : { foo : Natural } ⩓ t) → v.foo : Natural ``` Which, obviously, can't work. With `Record...

@Gabriel439: Thanks, seems like this was already considered as part of #494. I probably used an example that wasn't very representative of what would be useful for me.

@german1608, don't know if you're still interested, but use this a lot, but I have my own implementation `dhall --aply` from your example. With the implementation I'm using, your example...

I've stumbled upon this while trying to create a self describing API. In the end I had to build custom combinators for this purpose so I'm glad it's getting some...

We should also apply our coding style to tests and benchmarks.

Alternative to removing an effect is to find a more practical definition. For example `Coroutine` could be useful, but its current definition is a proof of concept, and not a...

We should look into [extensible-effects](https://hackage.haskell.org/package/extensible-effects), they seem to have figured some things out already.

I think that PR #25 made Coroutines much more useful for real applications.

Spec v0.8 also introduced `~/.local/bin`. There just isn't an environment variable override for it. It seems that they are slowly adopting Systemd's `file-hierarchy(7)`, which already did define `~/.local/bin`. I'm guessing...

I was thinking about this for a while. My idea was to create new module `Data.Text.Template.Parse` that would expose following: ```Haskell data ParseOptions = ParseOptions { bracketsRequired :: Bool ,...