-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
std::rt::task::TaskType fields made private, used in rust-mozjs #10065
Comments
I originally added this to the C++ runtime (and corresponding Rust types) in order to allow SpiderMonkey's garbage collection to see the bounds of Rust's stack. Exposing this information in some fashion is vital. |
I think it's fine if these are made public again. |
Yeah, it's fine for them to be public - whatever works for servo, as long as it's understood that |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Dec 17, 2022
fix: not suggest seek_to_start_instead_of_rewind when expr is used changelog: [`seek_to_start_instead_of_rewind`]: No longer lints, if the return of `seek` is used. [rust-lang#10096](rust-lang/rust-clippy#10096) <!-- changelog_checked --> Fixes rust-lang#10065
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
0ada7c7 made private the
current_stack_segment
field ofstd::rt::task::TaskType
that is used by rust-mozjs’s rust.rs#L69.Should this really be private? Or should rust-mozjs use something else? (I have no idea what this code is doing, I’m upgrading Rust-in-Servo to get an unrelated bug fix.)
The text was updated successfully, but these errors were encountered: