Clarification:
[Tim]
>>> Catching likely errors is a benefit for the user.
[Greg Ewing]
>> What evidence is there that this particular "likely error" is ..
[Tim]
> Nobody said it was likely. ...
Ha! I did! But not in Greg's sense. It was originally in the sense of "if
we see it, it's almost certainly an error on the part of the user", not that
"it's likely we'll see this". This is in the same sense that Python
considers
x = float(i,,)
or
x = for i [1,2,3]
to be likely errors -- you don't see 'em often, but they're most likely
errors on the part of the user when you do.
back-to-the-more-mundane-confusions-ly y'rs - tim
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