http://bugzilla.gdcproject.org/show_bug.cgi?id=165
--- Comment #2 from Ketmar Dark <ket...@ketmar.no-ip.org> --- Created attachment 79 --> http://bugzilla.gdcproject.org/attachment.cgi?id=79&action=edit hackfix for 'aliased import' segfault aaaah, got it! it's caused by double call to ImportStatement::semantic(). current DMD checks if there was only one call (with assertion), but i'm too lazy to track this to other places (i suspect there are alot of such 'double calls' scattered across 2.065 codebase anyway), so i just added a simple hack that bails out of analyser if it sees that something was already done. don't know if it will cause any problems for you, but for me it at least allows to build my project successfully (and the project actually works). not sure if it worth a "proper" fix anyway, as 2.065 codebase is soon ;-) to be replaced. side note: seems that not so many people does aliased imports is scope guards. -- You are receiving this mail because: You are watching all bug changes.
