Marcel van Lohuizen
Marcel van Lohuizen
The use of `ResolveReferences` will not generate something that is identical to the original in the general case. For instance, consider this counterexample ``` a: string b: a ``` is...
> The type in the cue is gradually narrowed, should the features that can narrow type range belong to data mode? That is a great question. It was a deliberate...
@wonderflow I would say it is the other way around. By example: Assume the following is represented by `root` ``` import "x/y" a: { b: y.S // has the value...
Note that `SelfContained` is a working name. We could reuse `ResolveReferences` to mean this. But it seems that the term `SelfContained` is a more appropriate name anyway, as it does...
Just FYI, I'm looking into a design to implement `SelfContained` now. Not trivial, but I'll giving it a serious whirl.
Current approach seems okay.
Would be good to know if any of our users are dependent on older Go versions, though.
@ElliotSwart thanks for the useful references. Of course xml is one of the obvious missing adaptors in CUE. The big reason why there is no xml adaptor yet is that...
There are several issues going on here: * a very expensive interface comparison in SpawnRef (results in about 25% of running time). * allocation of `closeInfo`s, about 40% of running...
This test is used for evaluation: https://gist.github.com/mpvl/ddd37202677606ab7edf80066e7f74fe