>> Would it be reasonable to raise an error or warning if a file's
>> close() method was called when the reference count was greater than
>> 1?
Barry> There could be lots of reasons why a file's refcount was greater
Barry> than 1 without threads entering into the picture.
Yeah, but they probably all represent some sort of bug. How about a warning
which is disabled by default but which the programmer can enable?
Skip
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