-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
zkvm: fix path to cmath in zkvm module #123858
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @m-ou-se (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
|
- Remove cmath from zkvm module since cmath was moved to sys and is shared by all platforms (see rust-lang#120109)
ad31b8a
to
861e213
Compare
Cool! @bors r+ rollup |
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#123654 (typeck: fix `?` suggestion span) - rust-lang#123807 (Remove `sys_common::thread`) - rust-lang#123834 (Don't do coroutine-closure-specific upvar analysis if tainted by errors) - rust-lang#123847 (Suppress `let else` suggestion for uninitialized refutable `let`s) - rust-lang#123857 (std::net: TcpListener shrinks the backlog argument to 32 for Haiku.) - rust-lang#123858 (zkvm: fix path to cmath in zkvm module) - rust-lang#123867 (Add `unsafe` to two functions with safety invariants) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#123858 - marijanp:fix-zkvm-cmath-path, r=joboet zkvm: fix path to cmath in zkvm module I don't know why the original author decided to use relative paths. I think it would be better to use `use crate::sys::cmath;` The according issue can be found here risc0/risc0#1647
I don't know why the original author decided to use relative paths.
I think it would be better to use
use crate::sys::cmath;
The according issue can be found here risc0/risc0#1647