Gabriella Gonzalez

@ocharles: `pipes-safe` does not do prompt finalization at all. The only way the computation promptly finalizes is if it terminates successfully without upstream or downstream terminating prematurely. You are correct...

@bos: Please merge this or give somebody else the commit bit. I just ran into several issues that this pull request fixed

I view the tradeoffs of URL-based imports differently: from my perspective URL imports provide a simpler user experience but they are not necessarily simpler to implement. In fact, they are...

@sjakobi: What I meant is that if one did something like this: ```dhall let x = 1 in ./example.dhall scope { x } ``` ... and `./example.dhall` contained: ```dhall x...

I believe if you want to import the variable as `Text` and produce an `Optional` result, the exact syntax would be: ```dhall Some (env:VAR as Text) ? None Text ```

@lisael: Yeah, the `?` operator accepts arbitrary Dhall expressions on either side (although it's only really useful if the left-hand side has some import embedded within it). So you could...

@sellout: The only way to solve it for URL imports is to limit the depth of the import tree. Otherwise you can have a server generate a synthetic import chain...

@ari-becker: You might be interested in this post on translating recursive types to Dhall: https://github.com/dhall-lang/dhall-lang/wiki/How-to-translate-recursive-code-to-Dhall You can see an example of this in the following branch which implements JSON support...

@ari-becker: You don't have to split up the union type in that way if it's harder for you to maintain. I only chose that exposition of how to do things...

@ocharles: Yeah, the only way this would work is if `List` became a keyword that had to be saturated with the element type instead of a built-in