Because not having standardised meanings at the same time as the
feature becomes available says to developers, "don't use the built-in
types in your annotations because we might give them a meaning
later...or maybe we won't...but in the meantime, you're going to need
to invent new spellings for lists, tuples, dicts, sets, strings, just
in case". As someone writing an annotation consumer, that comes across
as an incredibly arbitrary decision that forces me to do a lot of
extra work.
No, you aren't going to have to invent new spellings. As per my previous email, this should be allowed:
def myfunc( NumTuples: [typepackage1(tuple(int)),
typepackage2("tuple(Number+))")
]):...
All you need to do is declare the fact that you are using the built-in types in a non-standard way by wrapping them in your own annotation constructor.
Paul Prescod
All you need to do is declare the fact that you are using the built-in types in a non-standard way by wrapping them in your own annotation constructor.
Paul Prescod
_______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
