-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
[9/n][vm-rewrite][Move] Update depth calculation calculation/caching to be threadsafe #21074
Open
tzakian
wants to merge
1
commit into
tzakian/vm-rewrite-adapter-8
Choose a base branch
from
tzakian/vm-rewrite-adapter-9
base: tzakian/vm-rewrite-adapter-8
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
b9aac05
to
eee4b44
Compare
df609c5
to
4c8450e
Compare
1ccd302
to
54cd0cc
Compare
4c8450e
to
e686658
Compare
cgswords
approved these changes
Feb 5, 2025
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
54cd0cc
to
c0cde3b
Compare
e686658
to
f52ecca
Compare
c0cde3b
to
3e31dcf
Compare
f52ecca
to
6c763a2
Compare
…to be threadsafe Switching the depth calculation of types to be lazily evaluated when we first encountered the value, coupled with shared package cache, and the types living in this shared package cache meant that the `depth` for a type needed to be made threadsafe since we may need to write to it in a parallel context. This does this by `RwLock`ing the `depth` field and then making the changes from there.
3e31dcf
to
72813de
Compare
6c763a2
to
aa3e12c
Compare
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.
Switching the depth calculation of types to be lazily evaluated when we first encountered the value, coupled with shared package cache, and the types living in this shared package cache meant that the
depth
for a type needed to be made threadsafe since we may need to write to it in a parallel context.This does this by
RwLock
ing thedepth
field and then making the changes from there.