I had this comment about a runtime issue in the previous thread that I guess I’d need to re-raise:
In short, presuming @ for Annotated works the same way as | for Union, if the type is a forward reference the entire annotation becomes an opaque forward reference under Format.FORWARDREF. This would potentially lose all of the metadata until the forward reference could be resolved (see the first example from that link).
Personally I prefer the explicit Annotated (both due to the runtime issues and for clarity), I would like it more if typing was a lighter import but I’d rather that be a driver for improving the import time of typing over adding more new syntax to avoid the import.