[article] Language Design Deal Breakers

[Dicebot]

On Monday, 27 May 2013 at 09:08:16 UTC, Walter Bright wrote:
> Are you arguing that notnull should be a core language feature 
> instead of a library one?

Can't day for deadalnix, but I'd argue it is much more useful as 
default behavior :P (does not matter, core or library, but we 
can't do defaults from library now)

NonNullable!T in library is good, but if programmer can forget to 
handle null case, he will also forget to use proper library type. 
Best thing about restrictive-by-default approach is that you keep 
getting compile-time errors if you forget something. By the way 
same goes for impure-by-default, mutable-by-default etc. The very 
need for automatic attribute inference shows why such design 
approach is not that wise.