gabby

@Nadrieril: Yes, any operator for unions can be implemented in terms of its dual operation on records. Also, to be pedantic, you would implement `\/` in terms of `/\`, not...

This requires a change to the pretty-printing API to fix. The issue is that `Dhall.Pretty.prettyCharacterSet` can only format the import using the `Pretty` instance for `Import`, since the type of...

Yeah, I'd be fine with removing HTTP headers so long as we explained how to do the same thing using `netrc` files (although I haven't actually checked yet if `netrc`...

@KAction: I think the most likely path forward is what I outlined in https://github.com/dhall-lang/dhall-lang/issues/739#issuecomment-726188100 In general, changes like these have to go through the standardization process

Yeah, it does not need to be treated as a reserved identifier since it's only used as part of an `as Location` modifier, so it can't be mistaken for an...

This seems like a safe built-in to add to me in the sense that it converts one opaque type (`Double`) into another opaque type (`Text`) and I can see the...

@Nadrieril: I think the main argument for `Double/round 3.1 0` not returning `3.0` is that `3.0` is 1 significant digit of precision when the user requested 0 significant digits via...

@ocharles: What change to the grammar do you propose to permit that parse?

@ocharles: Yeah, that seems reasonable to me

@Nadrieril: Oh yeah, that's a good point. It would lead to an ambiguous parse