On 9/17/12 1:15 PM, bearophile wrote:
Andrei Alexandrescu:

Our position is that NonNull is only one of several instances of a
much more general pattern, which can be addressed with @disable once
it is properly tracked inside constructors.

It's an iterative process: some people invent a feature and put in a
language, others find it partially implementable in libraries and/or
useful if generalized. Later someone maybe finds that one of the library
constructs is so commonly used that adding some built-in sugar (like a
trailing @) makes code shorter and nicer, and so on and on :-)

Bye,
bearophile

That sounds nice but it turns out it's not the way @disable came about.

Andrei

Reply via email to