bearophile wrote:
Jeremie Pelletier:
Flow analysis must be implemented by the compiler, nonnull references
can be enforced by a runtime wrapper
The point of nonnull references is all in its compile-time enforced constraints.
Besides DMD must have some basic flow analysis already since it do
Jeremie Pelletier:
> Flow analysis must be implemented by the compiler, nonnull references
> can be enforced by a runtime wrapper
The point of nonnull references is all in its compile-time enforced constraints.
> Besides DMD must have some basic flow analysis already since it does
> notice wh
bearophile wrote:
Don:
Maybe if D had better flow analysis, the demand for
non-nullable references wouldn't be so great.
I know a good enough C# programmer that agrees with you, he says that thanks to
the flow analysis C#compiler performs, the need for non-nullable references is
not so stro
Don:
> Maybe if D had better flow analysis, the demand for
> non-nullable references wouldn't be so great.
I know a good enough C# programmer that agrees with you, he says that thanks to
the flow analysis C#compiler performs, the need for non-nullable references is
not so strong.
> (Neither
Walter Bright wrote:
Denis Koroskin wrote:
> On Sat, 26 Sep 2009 22:30:58 +0400, Walter Bright
> wrote:
>> D has borrowed ideas from many different languages. The trick is to
>> take the good stuff and avoid their mistakes .
>
> How about this one:
>
http://sadekdrobi.com/2008/12/22/null