Profpatsch
Profpatsch
Because of the reasons I listed above. It’s a very brittle feature.
That’s true, but also why compilers usually warn about variable shadowing.
I think the point about variable shadowing (and compilers warning about it) is still valid, because in >90% of cases it’s not what users want to do, but hints at...
I don’t think the idea is to guess types. From #326: ```dhall ./foo.json as JSON : List { name : Text, age : Natural } ```
I think the last section was about how JSON should be typed in dhall by default (yet still with deterministic rules what gets which type). For example the aforementioned ```...
Untagged unions should be different from sum types in my opinion. I wouldn’t have expected `dhall-to-json` to throw the tags away to be honest.
Yeah, but the generated nix code is still not valid nix syntax, this generates ``` Foo/Bar: Foo/Bar ```
Ping. I’m trying to write a flycheck plugin for emacs, so I’d like to show the user all files that can’t be imported. One intermediate solution would be to try...
> I have higher priority improvements I'd like to address (like performance) Very valid. > Additional improvements will require me to overhaul Dhall's exception system The multiple error messages changes...
Updating `dhall-flycheck` to latest dhall, and I was bitten by errors being exceptions again. It’s just not possible to correctly wrap dhall at the moment and being sure that errors...