[Issue 6372] New: data loss due to possible bug in garbage collector

http://d.puremagic.com/issues/show_bug.cgi?id=6372 Summary: data loss due to possible bug in garbage collector Product: D Version: D2 Platform: Other OS/Version: Linux Status: NEW Severity: critical Priority: P2

[Issue 3934] Some untidy attributes

http://d.puremagic.com/issues/show_bug.cgi?id=3934 --- Comment #20 from bearophile_h...@eml.cc 2011-07-24 05:51:32 PDT --- This is accepted by DMD 2.054, but if it's not meaningful in D then I suggest to statically disallow it, as the other examples: class Foo {} class Bar : public Foo {}

[Issue 6373] New: More descriptive 'hidden by X is deprecated' error

http://d.puremagic.com/issues/show_bug.cgi?id=6373 Summary: More descriptive 'hidden by X is deprecated' error Product: D Version: D2 Platform: All OS/Version: All Status: NEW Keywords: diagnostic Severity: minor

[Issue 6365] AutoTupleDeclaration

http://d.puremagic.com/issues/show_bug.cgi?id=6365 --- Comment #15 from Kenji Hara k.hara...@gmail.com 2011-07-24 06:41:36 PDT --- I found a conflict like follows: (double, string) (i, j) = tuple(1.2, a); (var, func)(var, var) = tuple(1.2, a); So it is bad. I clean up syntax, and update

[Issue 6365] AutoTupleDeclaration

http://d.puremagic.com/issues/show_bug.cgi?id=6365 --- Comment #16 from bearophile_h...@eml.cc 2011-07-24 07:24:53 PDT --- (In reply to comment #15) I clean up syntax, and update patch. https://github.com/9rnsr/dmd/compare/expandTuples...declarationTuple Thank you. How does it behave for:

[Issue 3934] Some untidy attributes

http://d.puremagic.com/issues/show_bug.cgi?id=3934 --- Comment #21 from Stewart Gordon s...@iname.com 2011-07-24 07:38:37 PDT --- (In reply to comment #20) This is accepted by DMD 2.054, but if it's not meaningful in D then I suggest to statically disallow it, as the other examples: class

[Issue 6365] AutoTupleDeclaration

http://d.puremagic.com/issues/show_bug.cgi?id=6365 --- Comment #17 from Kenji Hara k.hara...@gmail.com 2011-07-24 07:38:49 PDT --- (In reply to comment #16) How does it behave for 0-tuples and 1-tuples? I think 1-element tuple expansion should be allowed. Now my patch's this support is

[Issue 3934] Some untidy attributes

http://d.puremagic.com/issues/show_bug.cgi?id=3934 klickverbot c...@klickverbot.at changed: What|Removed |Added CC||c...@klickverbot.at

[Issue 3934] Some untidy attributes

http://d.puremagic.com/issues/show_bug.cgi?id=3934 --- Comment #23 from Stewart Gordon s...@iname.com 2011-07-24 07:54:03 PDT --- (In reply to comment #22) (In reply to comment #21) (In reply to comment #20) class Foo {} class Bar : public Foo {} void main() {} There are no attributes

[Issue 3934] Some untidy attributes

http://d.puremagic.com/issues/show_bug.cgi?id=3934 --- Comment #24 from kenn...@gmail.com 2011-07-24 09:09:15 PDT --- (In reply to comment #20) This is accepted by DMD 2.054, but if it's not meaningful in D then I suggest to statically disallow it, as the other examples: class Foo {}

[Issue 5299] Protected inheritance is semantically undefined.

http://d.puremagic.com/issues/show_bug.cgi?id=5299 Stewart Gordon s...@iname.com changed: What|Removed |Added CC||s...@iname.com ---

[Issue 177] Remove inheritance protection

http://d.puremagic.com/issues/show_bug.cgi?id=177 Stewart Gordon s...@iname.com changed: What|Removed |Added Status|REOPENED|RESOLVED

[Issue 5299] Protected inheritance is semantically undefined.

http://d.puremagic.com/issues/show_bug.cgi?id=5299 Stewart Gordon s...@iname.com changed: What|Removed |Added CC||ben...@tionex.de ---

[Issue 6365] AutoTupleDeclaration

http://d.puremagic.com/issues/show_bug.cgi?id=6365 --- Comment #18 from bearophile_h...@eml.cc 2011-07-24 11:14:57 PDT --- (In reply to comment #17) // 1-tuple expansion auto (x1) = [10]; Are you sure you want to use that syntax? A syntax more similar to the Python one is: auto (x1,) =

[Issue 6365] AutoTupleDeclaration

http://d.puremagic.com/issues/show_bug.cgi?id=6365 --- Comment #21 from Kenji Hara k.hara...@gmail.com 2011-07-24 12:20:00 PDT --- (In reply to comment #20) This too is valid D code: auto a = [1, 2,]; I didn't know that. Thank you. cut In this case, TupleDeclaration syntax is similar to

[Issue 6374] [CTFE] Cannot subscript using pointer to array

http://d.puremagic.com/issues/show_bug.cgi?id=6374 --- Comment #1 from kenn...@gmail.com 2011-07-24 14:53:02 PDT --- Note that this prevents std.array.appender from being CTFE-able, because it contains the code: _data.arr.ptr[len] = cast(Unqual!T)item; // -- error

[Issue 6376] Throwing exception or assertion failure causes segfault or memory error due to ASLR on Mac OS X 10.7

http://d.puremagic.com/issues/show_bug.cgi?id=6376 --- Comment #1 from kenn...@gmail.com 2011-07-24 15:33:29 PDT --- See also discussion in http://thread.gmane.org/gmane.comp.lang.d.general/61384. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are

[Issue 6377] New: std.conv.to should check range when changing signedness

http://d.puremagic.com/issues/show_bug.cgi?id=6377 Summary: std.conv.to should check range when changing signedness Product: D Version: D2 Platform: Other OS/Version: Windows Status: NEW Severity: normal

[Issue 6377] std.conv.to should check range when changing signedness

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

[Issue 6377] std.conv.to should check range when changing signedness

http://d.puremagic.com/issues/show_bug.cgi?id=6377 --- Comment #2 from Vladimir Panteleev thecybersha...@gmail.com 2011-07-24 16:08:26 PDT --- I thought the whole point of std.conv.to for integer to integer conversions is to make them safe, and make sure that the value - as interpreted from

[Issue 6376] Throwing exception or assertion failure causes segfault or memory error due to ASLR on Mac OS X 10.7

http://d.puremagic.com/issues/show_bug.cgi?id=6376 klickverbot c...@klickverbot.at changed: What|Removed |Added CC||c...@klickverbot.at