> From: Joshua Marshall > > I don't think I'm convinced; the same argument could be used > for integers (if it doesn't make sense to create a sort of > boolean which isn't in the set { true, false }, then it > doesn't make sense to create a sort of integer which isn't in > the set { ..., -2, -1, 0, 1, 2, ... }). And maybe it > doesn't, but this isn't the only reason for subclassing. > Another reason for subclassing is to create items which can > act like existing objects, but which have some additional behavior. So should we be able to subclass NoneType so as to break the invariant that there is one and only one None instance? Tim Delaney
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4