Timeline for Is it conventional to raise a NotImplementedError for methods whose implementation is pending, but not planned to be abstract?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2017 at 23:46 | history | edited | Robert Harvey | CC BY-SA 3.0 | deleted 4 characters in body |
| S Jun 2, 2017 at 0:36 | history | suggested | TemporalWolf | CC BY-SA 3.0 | Added update to documentation which reinforces answer. |
| Jun 1, 2017 at 20:27 | review | Suggested edits | |||
| S Jun 2, 2017 at 0:36 | |||||
| Dec 16, 2015 at 11:15 | vote | accept | gerrit | ||
| Mar 10, 2014 at 20:43 | comment | added | Ben Lee | +1, but I'd also add that for this kind of convention, a little documentation can go a long way. Like a one-line note in a dev wiki, repo readme, or style guideline -- something like that -- explaining what you use this exception for. | |
| Mar 5, 2014 at 21:00 | history | answered | Robert Harvey | CC BY-SA 3.0 |