Antoine Pitrou <solipsis at pitrou.net> writes: > On Fri, 17 Jul 2015 06:59:16 +1000 > Ben Finney <ben+python at benfinney.id.au> wrote: > > > > +1. > > > > These checks are a good thing, but they belong in a linter tool not as > > aliases in the API. > > Practicality beats purity. Unless you have been actually *bitten* by > those checks I don't think there's any serious reason to complain. By definition, advocating to not add cruft to an API is going to be in advance of being bitten by those additions. Your position seems to be, then, that any complaint about additions to an API can be dismissed out of hand. I hope that's not what you mean, but I can't see what else you could be saying. -- \ “Of all classes the rich are the most noticed and the least | `\ studied.” —John Kenneth Galbraith, _The Age of Uncertainty_, | _o__) 1977 | Ben Finney
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