Skip to content

fix: update an unsafe code in reader to use a set_len(0) and preven…#12

Merged
Retype15 merged 1 commit into
mainfrom
fix-apply-unsafe-code-in-reader-safety-rules
Dec 23, 2025
Merged

fix: update an unsafe code in reader to use a set_len(0) and preven…#12
Retype15 merged 1 commit into
mainfrom
fix-apply-unsafe-code-in-reader-safety-rules

Conversation

@Retype15

Copy link
Copy Markdown
Member

fix: Update an unsafe code in reader to use a set_len(0) and prevent ManuallyDrop in step 4 to prevent memory leaks.
Changed result_buffer.as_mut_ptr() as usize to result_buffer.as_mut_ptr().addr() that is a better way to get this pointer as usize.

…t `ManuallyDrop` in step 4 to prevent memory leaks.

Changed `result_buffer.as_mut_ptr() as usize` to `result_buffer.as_mut_ptr().addr()` that is a better way to make this.
@Retype15 Retype15 added the bug Something isn't working label Dec 23, 2025
@Retype15 Retype15 linked an issue Dec 23, 2025 that may be closed by this pull request
@Retype15 Retype15 merged commit 22de78a into main Dec 23, 2025
4 checks passed
@Retype15 Retype15 mentioned this pull request Dec 23, 2025
@Retype15 Retype15 deleted the fix-apply-unsafe-code-in-reader-safety-rules branch December 29, 2025 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Leaks

1 participant