gabby

I think it might be fine to make the number of retries configurable (either via the API, the command line, or both), but my intuition is that the default number...

@PierreR: This issue is probably more appropriate for the `dhall-haskell` repository because that i where the `dhall-lsp-server` implementation resides. This repository is for the VSCode client plugin, so I'll relocate...

I believe the simplest solution to this problem would be for the language server to maintain the cache in memory (already decoded) so that decoding costs only need to be...

The main reason against aligning `=` and `:` is because it could potentially lead to large diffs when adding/removing fields

@TravisWhitaker: No decision is ever really set in stone (we can always propose reverting behavior), but we'd need a sufficiently strong demand from users to justify reverting the original change....

@kukimik: This is more specifically an issue with the Haskell implementation of Dhall. See: https://github.com/dhall-lang/dhall-haskell/issues/2200

I'd probably be okay with a solution that looks visually appealing, but I'm familiar with Haskell's support for this and even after using it extensively I never found it pleasing....

@lisael: Yeah, I think this is a good idea. The only issue I can think of is that `dhall freeze` or the language server's support for freezing imports wouldn't work...

@lisael: Don't worry too much about it. I don't think it's a deal-breaker if `dhall freeze` doesn't support it

Also, playing devil's advocate against myself: there is one issue that this leads to, which is how people would develop and distribute code for parsing imports. For example, would the...