On 4/26/2014 3:01 PM, Timon Gehr wrote:
On 04/26/2014 10:32 PM, Daniel N wrote:
The disadvantage of this is that it forces one .di file per namespace,
whereas in C++ people frequently use different namespaces within the
same file.
Andrei
I would argue that this restriction is a benefit not a disadvantage,
Why on earth would precluding an organisation of the binding in the file system
mirroring the C++ side be a benefit?
I've also been arguing that the druntime import hierarchy for imports of C
system headers should match the layout of how a C user typically #include's them.
I.e. we should not be trying to fix the hierarchy of C include's, and we
shouldn't for C++, either.
