https://issues.dlang.org/show_bug.cgi?id=16423
--- Comment #9 from Ketmar Dark <ket...@ketmar.no-ip.org> --- (In reply to Steven Schveighoffer from comment #8) > But there may be code out there which expects Object.factory to work, and in > some cases, it will not. and there is. some of my UI parsers *depends* on the fact that class list and factory are there. i did that exactly to avoid manual registering of UI classes, which is highly error-prone. that is, some features are not removed 'cause there *may* be the code that depends on those. now there *is* the code that depends on full module/class infos and factory. this alone should rule "let's remove object.factory" out. let's see if real code has more weight than imaginary code. ;-) --