On 1/28/2017 11:43 PM, Lewis wrote:
I wonder though, would it make sense to make differing case in import statements a compiler error? And possibly give it a similar switch to optlink for ignoring case if need be? I hit this error because of a typo in one of my import statements, but the error message I got back from the linker didn't do a good job of pointing out my mistake (as is understandably true for most linker errors). For a simple and easy-to-catch typo, it seems like we could provide a better error message by catching this in the compiler :)
The best practice recommendation is to use all lower case in import names. This means you won't get any surprises porting to/from Windows file systems. Some people insist on using mixed case import names, and that's their choice. After all, D is a systems programming language.
I'd also stay away from using non-ascii characters in import names.
