Skip to content

Conversation

rachgreen33
Copy link
Contributor

@rachgreen33 rachgreen33 commented Sep 16, 2025

This change aligns with the V8 team's recommendation of setting flags this way through their API, rather than directly referencing v8::internal::v8_flags.

Signed-off-by: Rachel Green <rachgreen@google.com>
@rachgreen33 rachgreen33 changed the title Feat: Update V8 flag initialization to use V8 API, and restore default liftoff behavior Chore: Update V8 flag initialization to use V8 API, and restore default liftoff behavior Sep 16, 2025
Signed-off-by: Rachel Green <rachgreen@google.com>
Signed-off-by: Rachel Green <rachgreen@google.com>
@rachgreen33 rachgreen33 changed the title Chore: Update V8 flag initialization to use V8 API, and restore default liftoff behavior Chore: Update V8 flag initialization to use V8 API Sep 16, 2025
Signed-off-by: Rachel Green <rachgreen@google.com>
@rachgreen33 rachgreen33 marked this pull request as ready for review September 17, 2025 17:18
Copy link
Contributor

@mpwarres mpwarres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also worth documenting in the PR description that V8 team recommends setting flags this way rather than directly referencing v8::internal::v8_flags.

Signed-off-by: Rachel Green <rachgreen@google.com>
@rachgreen33 rachgreen33 requested a review from mpwarres October 3, 2025 15:27
@mpwarres mpwarres merged commit f3f9969 into proxy-wasm:main Oct 20, 2025
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants