[Issue 10177] New: irrelevant compiler error messages: should stop semantic3 passes after 1st error is encountered

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=10177

           Summary: irrelevant compiler error messages: should stop
                    semantic3 passes after 1st error is encountered
           Product: D
           Version: D2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DMD
        AssignedTo: nobody at puremagic.com
        ReportedBy: thelastmammoth at gmail.com


--- Comment #0 from thelastmammoth at gmail.com 2013-05-26 11:17:05 PDT ---
In a number of cases I get large compile error messages after running rdmd
main.d

Upon inspection, running with -v reveals that the irrelevant error messages are
in subsequent semantic3 passes:

semantic3 module_with_relevant_error
relevant error (eg: Error: no property 'x' for type 'y')
semantic3 module_with_irrelevant_error 
irrelevant error (only coming from the fact that there was an error in a prior
semantic pass)
...
and the list goes on for large number of lines.

Why not just stop semantic3 passes at 1st error occurence ?
or at least only show those by default?

in all cases i've encountered all that was needed for me to see was the 1st
faulty semantic3 pass, all other was irrelevant artifacts stemming from that.

I tried to reduce my case through dustmite with no success. Hopefully this is
clear enough.

(posted on
http://forum.dlang.org/post/mailman.1443.1369088668.4724.digitalmars-d-learn@puremagic.com
but got no answer)

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------