Profpatsch
Profpatsch
And another one, we also need to quote field selectors.
> ### We would like to make import lists less granular > I question this requirement because I'm not convinced that granular imports are the norm. Ideally, in a form...
Maybe the software of http://pursuit.purescript.org/ can be adapted for that purpose.
I temporary “fixed” it by commenting out this line: https://github.com/dhall-lang/dhall-haskell/blob/a9043ea193fe47f14c6eb83afeaf7c89d385a3b5/nix/shared.nix#L105-L106 It wasn’t easy to figure out where to pull to make the tests go away, even though I consider myself...
Esp. the whole extension business looks like quite a non-abstraction to me, that could be easier solved by some functions.
We should disallow `/` in the keys for that and tell the user that they should use nested records instead.
> But in @kowainik we solved all these problems, and now bidirectional codecs are as powerful and convenient enough as classic `ToJSON/FromJSON` typeclasses. Would love to see a blogpost on...
> This will probably require a couple of breaking changes to Dhall's exception hierarchy to leave less room for error. I've tried a few "simple" fixes, none of which worked...
Yes, that was the issue I was thinking about.
It’s usually a bad idea to make the semantics of source change if it’s invoked differently.