Timeline for Designing around shallow constness with inheritance
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 1, 2015 at 16:20 | history | edited | Doc Brown | CC BY-SA 3.0 | deleted 91 characters in body |
| Oct 1, 2015 at 15:04 | history | edited | Doc Brown | CC BY-SA 3.0 | added 521 characters in body |
| Oct 1, 2015 at 14:59 | comment | added | Doc Brown | @EmilyL.: see my edit. | |
| Oct 1, 2015 at 14:58 | history | edited | Doc Brown | CC BY-SA 3.0 | added 521 characters in body |
| Oct 1, 2015 at 14:43 | comment | added | Emily L. | And how would I pass an Image where a ConstImage is expected then? The two don't become convertible just because they share a common baseclass (however both become convertible to the base class, if you suggest using IImage where ConstImage is desired, that just becomes contrieved and essentially the same as inheriting Image from ConstImage). | |
| Oct 1, 2015 at 14:42 | history | edited | Doc Brown | CC BY-SA 3.0 | added 4 characters in body |
| Oct 1, 2015 at 14:40 | comment | added | Doc Brown | An IImage will only contain common methods Image and ConstImage, so IImage will not provide any non-const operators. | |
| Oct 1, 2015 at 14:31 | history | answered | Doc Brown | CC BY-SA 3.0 |