[Issue 7584] contract checking is too conservative for inherited contracts

2012-02-26 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 deadalnix changed: What|Removed |Added CC||deadal...@gmail.com --- Comment #1 from de

[Issue 7584] contract checking is too conservative for inherited contracts

2012-02-26 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 --- Comment #2 from timon.g...@gmx.ch 2012-02-26 05:03:25 PST --- Again, give an example. Your claim is not true. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: --

[Issue 7584] contract checking is too conservative for inherited contracts

2012-02-26 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 --- Comment #3 from deadalnix 2012-02-26 07:35:07 PST --- (In reply to comment #2) > Again, give an example. Your claim is not true. In Foo, you sated, by contract, that the function must return 0. Any piece of code using an object of type Foo

[Issue 7584] contract checking is too conservative for inherited contracts

2012-02-26 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 --- Comment #4 from timon.g...@gmx.ch 2012-02-26 08:17:35 PST --- LSP is not violated. That is the point. The rules proposed here are sufficient to guarantee LSP. The rules that are currently employed are too conservative. Think about it. void

[Issue 7584] contract checking is too conservative for inherited contracts

2012-02-26 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 --- Comment #5 from deadalnix 2012-02-26 08:28:57 PST --- (In reply to comment #4) > LSP is not violated. That is the point. The rules proposed here are sufficient > to guarantee LSP. The rules that are currently employed are too conservative.

[Issue 7584] contract checking is too conservative for inherited contracts

2012-05-02 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 7584] contract checking is too conservative for inherited contracts

2012-05-03 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 --- Comment #7 from timon.g...@gmx.ch 2012-05-03 02:20:30 PDT --- (In reply to comment #6) > Out contracts are "anded" together, meaning that *all* out contracts must pass > in an inheritance hierarchy. Out contracts in overriding functions do n

[Issue 7584] contract checking is too conservative for inherited contracts

2012-05-03 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 --- Comment #8 from deadalnix 2012-05-03 04:18:22 PDT --- (In reply to comment #6) > Out contracts are "anded" together, meaning that *all* out contracts must pass > in an inheritance hierarchy. Out contracts in overriding functions do not > ov

[Issue 7584] contract checking is too conservative for inherited contracts

2012-05-03 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7584 --- Comment #10 from timon.g...@gmx.ch 2012-05-03 08:53:53 PDT --- (In reply to comment #9) > (In reply to comment #0) > > IIRC, this is how contract inheritance works in Spec#. Spec# is (ahead of) > > state of the art in this area. > > Accordi