[Issue 5110] Excess attribute propagation of structs and classes

http://d.puremagic.com/issues/show_bug.cgi?id=5110 Walter Bright changed: What|Removed |Added CC||zan77...@nifty.com --- Comment #6 from

[Issue 5110] Excess attribute propagation of structs and classes

http://d.puremagic.com/issues/show_bug.cgi?id=5110 Walter Bright changed: What|Removed |Added CC||tomeks...@gmail.com --- Comment #5 fro

[Issue 5110] Excess attribute propagation of structs and classes

http://d.puremagic.com/issues/show_bug.cgi?id=5110 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 5110] Excess attribute propagation of structs and classes

http://d.puremagic.com/issues/show_bug.cgi?id=5110 --- Comment #3 from Shin Fujishiro 2010-10-24 02:18:33 PDT --- Created an attachment (id=793) Patch against dmd r727, passed dmd/druntime/phobos tests The proposed patch implements the said rule. The patch limits STC propagation via Scope's

[Issue 5110] Excess attribute propagation of structs and classes

http://d.puremagic.com/issues/show_bug.cgi?id=5110 --- Comment #2 from Shin Fujishiro 2010-10-24 02:09:16 PDT --- Created an attachment (id=792) Testcases Since nothrow, pure and @disable are one-way, non-revertible attributes, the language should not force them to be propagated IMO. So, str

[Issue 5110] Excess attribute propagation of structs and classes

http://d.puremagic.com/issues/show_bug.cgi?id=5110 --- Comment #1 from Shin Fujishiro 2010-10-24 02:05:22 PDT --- The current ClassDeclaration uses the following black list for masking attributes to propagate over its members: sc->stc &= ~(STCfinal | STCauto | STCscope | S