Author nadeem.vawda
Recipients jcea, nadeem.vawda, python-dev, serhiy.storchaka, victorhooi
Date 2012-09-30.22:17:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349043440.26.0.884715355735.issue16034@psf.upfronthosting.co.za>
In-reply-to
Content
> Recursive inline _check_can_read() will be enough. Now this check calls 4 Python functions (_check_can_read(), readable(), _check_non_closed(), closed). Recursive inlining only readable() in _check_can_read() is achieved significant but less (about 30%) effect.

I've inlined readable() into _check_can_read() [3.3: 4258248a44c7 | default: abb5c5bde872]. This seems like a good balance between maximizing our performance in edge cases and not turning the code into a mess in the process ;)

Once again, thanks for your contributions!
History
Date User Action Args
2012-09-30 22:17:20nadeem.vawdasetrecipients: + nadeem.vawda, jcea, python-dev, serhiy.storchaka, victorhooi
2012-09-30 22:17:20nadeem.vawdasetmessageid: <1349043440.26.0.884715355735.issue16034@psf.upfronthosting.co.za>
2012-09-30 22:17:20nadeem.vawdalinkissue16034 messages
2012-09-30 22:17:20nadeem.vawdacreate