[Issue 2050] interfaces should allow final methods with body

2015-06-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=2050 Andrei Alexandrescu changed: What|Removed |Added Version|unspecified |D2 --

[Issue 2050] interfaces should allow final methods with body

2011-06-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2050 yebblies changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 2050] interfaces should allow final methods with body

2010-07-07 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2050 Rob Jacques changed: What|Removed |Added CC||sandf...@jhu.edu --- Comment #12 from Ro

[Issue 2050] interfaces should allow final methods with body

2009-04-04 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2050 --- Comment #11 from and...@metalanguage.com 2009-04-04 10:58 --- (In reply to comment #9) > (In reply to comment #0) > This seems to break composability: > > interface I1 { final int foo() {return 1;} } > interface I2 { final int fo

[Issue 2050] interfaces should allow final methods with body

2009-04-04 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2050 --- Comment #10 from sandf...@jhu.edu 2009-04-04 10:01 --- (In reply to comment #0) > Consider: > > interface Foo > { > void bar(); > final void baz() { bar; bar; } > } How is this superior to the current interface + mixin a

[Issue 2050] interfaces should allow final methods with body

2009-04-04 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2050 --- Comment #9 from sandf...@jhu.edu 2009-04-04 09:53 --- (In reply to comment #0) This seems to break composability: interface I1 { final int foo() {return 1;} } interface I2 { final int foo() {return 2;} } class A: I1, I2 {} Whos