Dhall-haskell: Dhall.Core.Project should store an ordered set of field projections

[ocharles]

Continuing from #518, which identifies that the Set currently used will loose field ordering.

[f-f]

@ocharles what’s the use case for this?

[ocharles]

For dhall format to retain the filed ordering. It was mentioned in #516 that Project probably shouldn't just be using a Set.

[MonoidMusician]

For what it’s worth, the way I’m modelling this in my dhall-purescript project is by using the same datatype used to represent records and unions, except over () instead of Expr ... (Expr is now parameterized over that functor too, so it can be ordered [(String, a)] or unordered Map String a, whatever.) I just think it conceptually works well to have the projection set represented in the same way as records themselves, and it seems to cost little.

[Gabriel439]

This was fixed by https://github.com/dhall-lang/dhall-haskell/pull/670