Marcel van Lohuizen

I was able to reproduce the problem. It only seems to occur with some value types and not others. That is why existing tests that do similar things did not...

Ah, of course. The cases where it worked there was a(n implicit) default value, like [...int]. > Also, this works, which is... interesting: This also makes sense. Basically, because the...

So depending on the exact definition of how we attribute errors after the comprehension rework, this Issue will be either a feature request or a bug. :).

I would suggest for now the proper way to do this is: ``` // Say hello! command: prompter: { ask: cli.Ask & { prompt: "What is your name?" response: string...

@eonpatapon the main benefit of this approach is to improve the parallelism. But I agree it generally can't hurt to consider it as a dependency. We were considering to fix...

See also #1593 , which seems to strongly indicate we should aways consider concrete values for the determination of dependencies of tasks. However, the current algorithm does seem to not...

`ResolveReferences` is implemented by switching to data mode, which would be causing this. You can try to not use `ResolveReferences` with tip, which includes the new self-containment logic.

I get `import "mod.com/p"` instead of `import "mod.com"`. But that aside. It is correct it will not resolve references within the exported tree within schema mode, because otherwise you are...

Aside from it not being correct, in general, it is not possible (when there are cycles), or may alternatively open you up for security concerns. (billion laughs attack), if you...

One problem with arbitrarily expanding references is that it can lead to a combinatorial explosion. @wonderflow, @leejanee: It would therefore be good to understand what the objective is. Can you...