Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-103583: Isolate CJK codec modules#103869
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Lifetime should be guaranteed, since each MultibyteCodecObjects owns areference the cjk codec module that owns the memory of theMultibyteCodec struct.
664f961
tof6ed5df
CompareThis approach exploits the dependency introduced ingh-103589; we know for sure that the _codec* extension modules will outlive _multibytecodec. This means we can store the cjk codec module state safely in the codec struct and modify the various codec handlers to accept the codec struct (iso. |
bedevere-bot commentedApr 26, 2023
🤖 New build scheduled with the buildbot fleet by@erlend-aasland for commitef983c4 🤖 If you want to schedule another build, you need to add the🔨 test-with-refleak-buildbots label again. |
BTW, I removed the |
erlend-aasland commentedApr 26, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@vstinner, you want to take a look? :) |
@erlend-aasland I will take a look by tomorrow |
(Pulling in main to get the latest ref. leak fixes by Jelle) |
bedevere-bot commentedApr 26, 2023
🤖 New build scheduled with the buildbot fleet by@erlend-aasland for commitdec79a7 🤖 If you want to schedule another build, you need to add the🔨 test-with-refleak-buildbots label again. |
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM, This is quite a complicated but nice approach. But nothing can be better than this.
Thanks for the hard work!
Thanks for the review, Dong-hee! Yes, it is complicated, but as shown in my competing PRs, other approaches are even more complicated. |
Well done@erlend-aasland! |
Thanks, Victor :) This was a tricky one! |
Uh oh!
There was an error while loading.Please reload this page.