http://d.puremagic.com/issues/show_bug.cgi?id=11284
Denis Shelomovskij <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Denis Shelomovskij <[email protected]> 2013-10-20 15:10:52 MSD --- (In reply to comment #0) > I regard these as user build system irregularities, not bugs. However, user > confusion over this, and frustration over "it worked in 2.063 and now I get > this error message, what's wrong" is very real. Hence, I propose the -allinst > switch which will generate code for all instantiated templates, like 2.063 > does. Every release "accept-invalid" bugs are fixed and incorrect user code that used to work become uncompileable (showing user his mistakes and making user happy :) ). If in this particular case invalid compilation actions are too common to be broken immediately: 1. Links to user complains are needed to proof its huge count. 2. We have to find and resolve our mistake (e.g. lack of docs) that causes D user to do such errors in building process. Also IMHO points 2, 3, and 4 from the description are obviously user build process bugs that have to be pointed out by a tool-chain like it do now to prevent the worst case of buildable but incorrectly working application. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
