Reply to John,
(2) The assumption that the D port will only use .net libs.
Thinking about it more (and in the context of the above) their might be some interesting results of D.NET. Could a D based .NET assembly transparently call into both .NET managed libs and unmanaged CRT style libs? How does the safed stuff map to the managed environment model? Could D provide a clean language for mixing native code (totally normal D), normal "C#" style managed code (using safed) and managed and CLR but unsafe code (C# has this as well IIRC)?
