doc/tutorial/basics: example for bottom doesn't match output about cue HOT 6 CLOSED

I experienced the same confusion on the types page, where the tool outputs messages like the following instead of something similar to what's shown in the docs:

non-concrete value (float)*:
    [...]

from cue.

The page on order being irrelevant also hits this issue since the example incidentally generates a bottom value.

from cue.

The example on the disjunctions page could also be updated to avoid hitting this, perhaps by adding an emit value of lossy so the tool doesn't try to export conn.

from cue.

All the information is there. I originally did print the full tree with errors as values, but that made it too hard to see the errors, when they were buried in large configs. I'm even worried this may happen when the errors are printed at the end, but that would be a compromise. Would that work better you think? A vet tool could be used to only validate if one wishes.

As for the non-concrete values, I think eval should print those by default, and then allow different modes for: raw, medium, complete, or so.

On a pedantic note: even though I keep the errors in the tree, theoretically, if a unification error (so not an incomplete error) occurs within a tree, the full tree fails.

from cue.

By default cue now prints non-concrete values when using eval.

cue eval -i can now be used to print (partially) evaluated output with errors. This is basically what is shown in the tutorial.

from cue.

This issue has been migrated to cue-lang/cue#17.

For more details about CUE's migration to a new home, please see cue-lang/cue#1078.

from cue.