[Issue 2050] interfaces should allow final methods with body

https://issues.dlang.org/show_bug.cgi?id=2050 Andrei Alexandrescu and...@erdani.com changed: What|Removed |Added Version|unspecified |D2 --

[Issue 2050] interfaces should allow final methods with body

http://d.puremagic.com/issues/show_bug.cgi?id=2050 yebblies yebbl...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 2050] interfaces should allow final methods with body

http://d.puremagic.com/issues/show_bug.cgi?id=2050 Rob Jacques sandf...@jhu.edu changed: What|Removed |Added CC||sandf...@jhu.edu ---

[Issue 2050] interfaces should allow final methods with body

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 {}

[Issue 2050] interfaces should allow final methods with body

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 foo()