> version 1.0 battle plan > > ======================= > > \- make 'not nil' the default (produce warnings instead of errors for a > smooth migration path)
That's great. What's the syntax for declaring possibly nil types? > \- case objects needs to be safe and need to support pattern matching ML/Rust style pattern matching? > \- sanctionize some macro implementation for interfaces While I greatly appreciate the use of the American/Oxford suffix, the word **sanction** needs no suffix here. I hope that whichever implementation is sanctioned works well with all of the other relevant language features of Nim. > \- implement a way to forward object type declarations across module > boundaries; C++ style That would be really useful, but as a hard blocker for 1.0?
