Don't implement string types as vector wrappers #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…added `clear`, `as(_mut)_ptr` and `remove` to `BumpBox<str>`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently strings are implemented as wrappers around their respective vector type.
If we instead implement string types as their own hierarchy, mirroring the vector types then we can reuse functions from
BumpStringtoFixedBumpStringup toBumpBox<str>.We still want to have
as_mut_vecfor strings. We do that by making all vectors and strings#[repr(C)]so we can soundly transmute between them.This PR also adds missing string methods.