Separate JsString into its own crate
#3831
Closed
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
HalidOdat
force-pushed
the
js-string-crate
branch
from
a1933a2 to
8cdbbf1
Compare
|
Most child PRs rebase to main when its parent PR is merged, but Github decided to close this somehow ¯\_(ツ)_/¯ |
|
Yeah, it's weird... It wouldn't allow me to change base manually, so I recreated the PR #3837 |
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.
Depends on #3450
This Pull Request is a continuation of the work on #3829 , by moving the string crate because the
ByteCompilerdepends on it.There are still some issues withFixed by making it point tojs_str!macro that constructs aJsStr, there is no$cratefor proc macros unfortunately 😢boa_engineotherwise you have to includeboa_stringeverywhere... If there is another solution for this, would love to hear it :)