There's another solution: to make D2/D3 itself flexible enough that you can implement
your own simple "extensions" to the type system, so you
>can actually implement not-nullable references by default. This isn't
impossible (there are many papers about this,
>it can be done in Scheme, etc).
"everything is possible with code" - its not the question of how to
start an plugin/dll based function from descent compiler steps... thats
too easy to even talk about
but how should the plugin-system work?
what compiler-functions should be changeable through plugins?
how do the different engine like parser, semantic analyser etc work
together with the plugin, etc.? that is the nearly impossible to answer
question - what do the LLVM-guys think about plugin like that
and firefox-plugins are far too easy in its possible feature-set
compared to what is needed to add an type to an compiler