gabby

@feliksik: The main thing I'm waiting for is to see how `json-to-dhall` evolves over the next few months based on feedback from users. For example, there was a recent change...

@f-f: I'm not sure. It's a very half-baked idea I had at one point, that's all 🙂

@feliksik: I would actually be fine baking in language support for JSON specifically instead of waiting for a more general solution. Dhall's future as a language is already intimately tied...

Also, they pointed out that this is the same issue as: https://github.com/dhall-lang/dhall-haskell/issues/1672

@ari-becker: The answer to your first question is that `a ? b ? c sha256:…` unambiguously parses as `a ? b ? (c sha256:…)` This is because the left argument...

@ari-becker: `https://example.com using ./headers.dhall` is a valid `import-type` in the grammar, which is why the parse is ambiguous

Yeah, this is the relevant pull request for adding hashes anywhere: https://github.com/dhall-lang/dhall-lang/pull/668

@sjakobi: I'm not aware of this feature at the record level, but as you noted in #961 there are languages that support this at the pattern level It's still not...

@Nadrieril: Yeah, it really comes down to whether or not it is difficult for other implementations to keep up with the standard. I personally have no issue implementing these features,...

@JAForbes: I don't have any objections to doing this; I just need help with the NPM-specific parts because I have never used NPM before. We should probably reserve the name...