Simon Jakobi

Sorting the fields is a part of β-normalizing record types and values: https://github.com/dhall-lang/dhall-lang/blob/master/standard/beta-normalization.md#records I don't think it should be a required part of import resolution – I think the field...

Here's the relevant parser for `Some`: https://github.com/dhall-lang/dhall-haskell/blob/7aed7cf286ef245ce34acad6301b4fe0cdcc5271/dhall/src/Dhall/Parser/Expression.hs#L294-L309 Not sure how to best improve the error though…

@Gabriel439 Actually that label doesn't really help users who want to try `merge` on its own: ``` ⊢ merge {=} Error: Invalid input (stdin):1:10: | 1 | merge {=} |...

Hmm, I'm no longer so sure about this one: The initial `Expr` is an `Annot` where the annotation may be any `expression` ``` annotated-expression = operator-expression [ whsp ":" whsp1...

It seems that `toMap {=} : a ? b` should actually be parsed as `(toMap {=} : a) ? b`. Is that right?

Since I'm working on related code in https://github.com/dhall-lang/dhall-haskell/pull/1954, I've also had another look at this issue. Since the core of the problem seems to be that we parse an `expression`...

Another instance of a flaky tests due to a network issue: https://github.com/dhall-lang/dhall-haskell/pull/1825#issuecomment-636372897

It's not a bug. Leading zeros are explicitly forbidden for `Natural` and `Integer` literals: https://github.com/dhall-lang/dhall-lang/blob/af28c56ab5458df1cdcdd90c8c30a83d5e00d33e/standard/dhall.abnf#L496-L502

See https://github.com/dhall-lang/dhall-lang/pull/898 for some background.

I'm transferring this issue to the `dhall-lang` issue tracker, because it's an issue with the Dhall spec.