Roger Peppe

What exact text would you suggest it prints in this case? In general `testscript` does not mention anything about what its command line was at all - there are other...

Here's my rationale for treating cue.Value as bottom, not top. To my mind the zero Value is strongly akin to a value that does not exist, as returned (for example)...

> > Making the zero Value behave more like top would require changing all of those, and hence it would be be a very significant breaking change that I don't...

> I'm saying that we could make the zero value be anything we want at this point I disagree. Although not documented, the current API has at least been stable...

> Ive used the top behavior a lot and it would be a badly breaking change to change it, Which aspect of the behaviour is that? The only current behaviour...

> * They could take a long time; shoud `.../foo` match all "foo" packages across all CUE modules ever published? > * They could require many requests to registries, particularly...

The way I see these rules is that they specify when a registry GC implementation MAY release an object, not whether it MUST, or even SHOULD. To my mind that's...

I guess my main question is, as someone would like to write client code that stores artifacts in an implementation-agnostic fashion, do the rules I've stated actually correspond correctly to...

One thing that my rules don't make clear (and that I'm not clear on myself tbh), is whether it's possible that an object pushed to the `blobs` endpoint can potentially...

Another thing that's not entirely clear to me: is it OK for a manifest to contain a reference to another manifest from the same repository as one of its layers/blobs?