This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author syl-nktaylor
Recipients ezio.melotti, serhiy.storchaka, syl-nktaylor, vstinner
Date 2020-12-07.22:06:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1607378763.26.0.383524646757.issue42593@roundup.psfhosted.org>
In-reply-to
Content
The build did seem to run, despite memset using fillchar without the explicit casting, so I assumed it did an implicit casting, but the original casting can be kept of course. With this build, my sample tests for 1-byte, 2-byte and 4-byte chars also ran ok, so again, I assumed memset did the casting.

As for the benchmarks, I haven't run them, but yes, it's likely the best way to find out the performance considerations I was asking about.
History
Date User Action Args
2020-12-07 22:06:03syl-nktaylorsetrecipients: + syl-nktaylor, vstinner, ezio.melotti, serhiy.storchaka
2020-12-07 22:06:03syl-nktaylorsetmessageid: <1607378763.26.0.383524646757.issue42593@roundup.psfhosted.org>
2020-12-07 22:06:03syl-nktaylorlinkissue42593 messages
2020-12-07 22:06:03syl-nktaylorcreate