<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">ping.</span><div><font color="#222222" face="arial, sans-serif"><br></font><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
I've posted a bugzilla entry <a href="http://d.puremagic.com/issues/show_bug.cgi?id=10177" target="_blank" style="color:rgb(17,85,204)">http://d.puremagic.com/issues/show_bug.cgi?id=10177</a> and finally managed to reduce to a small test case.</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
So will the proposed method improve error reporting?</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Is there any case where it might hurt?</div><br><div class="gmail_quote">
On Mon, May 20, 2013 at 3:24 PM, Timothee Cour <span dir="ltr"><<a href="mailto:thelastmammoth@gmail.com" target="_blank">thelastmammoth@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In a number of cases I get very large compile error messages after running rdmd main_module.d<div><br></div><div>Upon inspection, running rdmd -v fun.d reveals that the irrelevant error messages are in different semantic3 passes:</div>
<div><div><br></div><div>semantic3 module_with_relevant_error</div><div>relevant error (eg: Error: no property 'x' for type 'y')</div><div>semantic3 module_with_irrelevant_error </div></div><div>irrelevant error (only coming from the fact that there was an error in a prior semantic pass)</div>
<div>...</div><div>and the list goes on for large number of lines.</div><div><br></div><div>Why not just start semantic3 passes at 1st error occurence ?</div><div>or at least only show those by default?</div><div><br></div>
<div>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.</div><div><br></div>
</blockquote></div><br></div>