> no, untyped can be used to (when instantiated), return either void or non-void
Correct, so it should be
> typed is after type/symbol resolution and untyped is before.
Which is different from "has a certain type / is in a certain type class".
Existing type(class)es should not replace `typed` as a return type, they should
narrow down its meaning.
> auto when void or some type, else:
> any when some type, else:
That would require changes to the type system, because ATM `void is any` is