[Issue 4518] New: to!string(enum w/invalid value) produces a somewhat unhelpful error

http://d.puremagic.com/issues/show_bug.cgi?id=4518 Summary: to!string(enum w/invalid value) produces a somewhat unhelpful error Product: D Version: D2 Platform: Other OS/Version: All Status: NEW Keywords:

[Issue 4519] New: variable shadowing error from std.format

http://d.puremagic.com/issues/show_bug.cgi?id=4519 Summary: variable shadowing error from std.format Product: D Version: D2 Platform: Other OS/Version: Windows Status: NEW Severity: regression Priority: P2

[Issue 4516] forward declaration of enum not supported

http://d.puremagic.com/issues/show_bug.cgi?id=4516 Leandro Lucarella llu...@gmail.com changed: What|Removed |Added CC||llu...@gmail.com

[Issue 4516] forward declaration of enum not supported

http://d.puremagic.com/issues/show_bug.cgi?id=4516 Don clugd...@yahoo.com.au changed: What|Removed |Added CC||clugd...@yahoo.com.au ---

[Issue 4514] Regression: Cannot cast from X* to X

http://d.puremagic.com/issues/show_bug.cgi?id=4514 --- Comment #3 from Leandro Lucarella llu...@gmail.com 2010-07-27 11:04:29 PDT --- (In reply to comment #1) Since this doesn't appear in the code, I'd doubt that that's the cause. I don't know how the compiler internals deals with this, but

[Issue 4520] add support for //! style documentation comments

http://d.puremagic.com/issues/show_bug.cgi?id=4520 --- Comment #2 from Trass3r mrmoc...@gmx.de 2010-07-27 11:13:46 PDT --- Well it's personal taste. As I said, only requires minimal changes to the lexer, Doxygen also uses /// and //!, so why not? It's just a proposal. -- Configure issuemail:

[Issue 4514] Regression: Cannot cast from X* to X

http://d.puremagic.com/issues/show_bug.cgi?id=4514 --- Comment #4 from Stewart Gordon s...@iname.com 2010-07-27 11:30:20 PDT --- I was going on the assumption that the _internal concept_ of this is the same in D1 and D2, and the difference is merely what the _keyword_ this means between the two

[Issue 4521] New: accepts-invalid Array-wise assignment on unallocated array is accepted

http://d.puremagic.com/issues/show_bug.cgi?id=4521 Summary: accepts-invalid Array-wise assignment on unallocated array is accepted Product: D Version: D2 Platform: Other OS/Version: All Status: NEW

[Issue 4520] add support for //! style documentation comments

http://d.puremagic.com/issues/show_bug.cgi?id=4520 Jonathan M Davis jmdavisp...@gmail.com changed: What|Removed |Added CC|

[Issue 4520] add support for //! style documentation comments

http://d.puremagic.com/issues/show_bug.cgi?id=4520 --- Comment #5 from Trass3r mrmoc...@gmx.de 2010-07-27 15:14:14 PDT --- The patch makes //! treated as a ddoc comment. As I already said, it's just a matter of taste. I prefer //! so I patched my dmd to be free to choose. I didn't claim this

[Issue 4522] New: Write outputs Unicode incorrectly (on Windows)

http://d.puremagic.com/issues/show_bug.cgi?id=4522 Summary: Write outputs Unicode incorrectly (on Windows) Product: D Version: D2 Platform: Other OS/Version: Windows Status: NEW Severity: normal Priority: P2

[Issue 4523] New: .remove method for Associative Arrays returns void in all cases

http://d.puremagic.com/issues/show_bug.cgi?id=4523 Summary: .remove method for Associative Arrays returns void in all cases Product: D Version: D2 Platform: Other OS/Version: All Status: NEW Severity:

[Issue 4523] .remove method for Associative Arrays returns void in all cases

http://d.puremagic.com/issues/show_bug.cgi?id=4523 --- Comment #1 from Andrej Mitrovic andrej.mitrov...@gmail.com 2010-07-27 18:16:27 PDT --- (In reply to comment #0) Example code errors out due to the .remove method returning void. This method should return boolean true if the key was in

[Issue 3463] Integrate Precise Heap Scanning Into the GC

http://d.puremagic.com/issues/show_bug.cgi?id=3463 --- Comment #57 from Leandro Lucarella llu...@gmail.com 2010-07-27 21:19:01 PDT --- I think there is a not-so-important bug in the DMD patch, the bits.length value looks like it needs to be divided by size_t.sizeof (which is odd, since in the

[Issue 3463] Integrate Precise Heap Scanning Into the GC

http://d.puremagic.com/issues/show_bug.cgi?id=3463 --- Comment #58 from Leandro Lucarella llu...@gmail.com 2010-07-27 21:23:34 PDT --- And another small comment about the Tango runtime patch, you add a binSize() function, but there is already a binsize[] array for the same purpose, you can

[Issue 4524] New: Bus error with nested struct

http://d.puremagic.com/issues/show_bug.cgi?id=4524 Summary: Bus error with nested struct Product: D Version: unspecified Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2

[Issue 4521] accepts-invalid Array-wise assignment on unallocated array is accepted

http://d.puremagic.com/issues/show_bug.cgi?id=4521 nfx...@gmail.com changed: What|Removed |Added CC||nfx...@gmail.com --- Comment #1

[Issue 3463] Integrate Precise Heap Scanning Into the GC

http://d.puremagic.com/issues/show_bug.cgi?id=3463 nfx...@gmail.com changed: What|Removed |Added Attachment #698 is|0 |1 obsolete|