-
Notifications
You must be signed in to change notification settings - Fork 27k
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
perf(turbopack): Use ResolvedVc
for turbopack-core
#73065
base: canary
Are you sure you want to change the base?
Conversation
01aa356
to
02047b3
Compare
02047b3
to
9f35866
Compare
@@ -11,10 +11,10 @@ use crate::ident::AssetIdent; | |||
|
|||
#[turbo_tasks::value(shared)] | |||
pub struct AnalyzeIssue { | |||
pub severity: Vc<IssueSeverity>, | |||
pub severity: ResolvedVc<IssueSeverity>, | |||
pub source_ident: Vc<AssetIdent>, |
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.
I couldn't use ResolvedVc<T>
here because of emit
function implementation in the file.
@@ -14,6 +14,7 @@ workspace = true | |||
|
|||
[dependencies] | |||
anyhow = { workspace = true } | |||
async-recursion = "1.1.1" |
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.
We shouldn't need this dependency anymore, it can be done with Box::pin
: #69762
What?
Use
ResolvedVc<T>
instead ofVc<T>
for struct fields inturbopack-core
Why?
How?