Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix SmolStrBuilder::push pushing null bytes on heap spill #89

Merged
merged 2 commits into from
Oct 23, 2024

Conversation

Veykril
Copy link
Member

@Veykril Veykril commented Oct 23, 2024

Fixes #88

@Veykril Veykril merged commit 5ffc900 into master Oct 23, 2024
1 check passed
@Veykril Veykril deleted the veykril/push-nlmzzlzoousl branch October 23, 2024 20:56
@Veykril Veykril changed the title Fix SmoLStrBuilder::push pushing null bytes on heap spill Fix SmolStrBuilder::push pushing null bytes on heap spill Oct 23, 2024
Enselic added a commit to cargo-public-api/cargo-public-api that referenced this pull request Oct 25, 2024
Our CI is currently failing because smol_str yanked 0.3.1. But it only
had a regular bug, not undefined behavior or a security hole:
rust-analyzer/smol_str#89

I don't want our CI to fail because of this, so let's allow yanked
crates. If a crate has a known security vulnerability, other cargo-deny
rules will catch it.
Enselic added a commit to cargo-public-api/cargo-public-api that referenced this pull request Oct 25, 2024
Our CI is currently failing because smol_str yanked 0.3.1. But it only
had a regular bug, not undefined behavior or a security hole:
rust-analyzer/smol_str#89

I don't want our CI to fail because of known regular bugs, so let's
allow yanked crates. If a crate has a known security vulnerability,
other lint rules will catch it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

v0.3.1 Null Bytes inserted if multi-byte unicode character forces builder to move to heap
1 participant