[Issue 3231] Function declared to return a type with its same name doesn't compile

2009-08-09 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3231 Stewart Gordon changed: What|Removed |Added Keywords||spec --- Comment #13 from Stewart G

[Issue 3231] Function declared to return a type with its same name doesn't compile

2009-08-09 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3231 --- Comment #14 from BCS 2009-08-09 11:59:46 PDT --- (In reply to comment #8) > @BCS > That case is indeed illegal, AND handled correctly by my fix. > Given that you are willing to redefine the language I have to ask; What is correctly?

[Issue 3231] Function declared to return a type with its same name doesn't compile

2009-08-09 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3231 --- Comment #15 from BCS 2009-08-09 12:02:15 PDT --- (In reply to comment #9) > > Better beware of hijacking vulnerabilities. class Foo {} class Bar { int Foo(){} // this would become a conflict with only an arbitrary resolution

[Issue 3238] New: Template function reference being made without the template body being generated

2009-08-09 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3238 Summary: Template function reference being made without the template body being generated Product: D Version: 2.031 Platform: x86 OS/Version: Windows Status: NEW

[Issue 3238] Template function reference being made without the template body being generated

2009-08-09 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3238 --- Comment #1 from Burton Radons 2009-08-09 22:22:42 PDT --- It turns out that there actually was a problem with the template; oddly enough the problem was one that causes the compiler to crash, unlike the banal semantic error here. So hav