On 4/24/17 11:03 AM, Mike Parker wrote:
DIP 1007 is titled "'future symbol' Compiler Concept".
https://github.com/dlang/DIPs/blob/master/DIPs/DIP1007.md
All review-related feedback on and discussion of the DIP should occur in
this thread. Due to DConf taking place during the review period, the
period will be extended by a week. The review period will end at 11:59
PM ET on May 15 (3:59 AM GMT May 16), or when I make a post declaring it
complete.
At the end of Round 1, if further review is deemed necessary, the DIP
will be scheduled for another round. Otherwise, it will be queued for
the formal review and evaluation by the language authors.
Thanks in advance to all who participate.
Destroy!
As I mentioned elsewhere, an intermediate step for a symbol that will
eventually need an override needs to be outlined. When you create a base
class member that conflicts with existing derived class members, the
mitigation may not simply be "you have to remove the derived function",
it could also be to override the future function. How do you override a
function that doesn't really exist?
I like the general idea, and it makes sense, even if it only affects a
small set of files (those that are heavily imported).
-Steve
