-
Notifications
You must be signed in to change notification settings - Fork 949
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
Revert to rust 1.63 #3217
Revert to rust 1.63 #3217
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3217 +/- ##
==========================================
+ Coverage 64.70% 65.26% +0.55%
==========================================
Files 81 81
Lines 38819 39479 +660
==========================================
+ Hits 25118 25764 +646
- Misses 13701 13715 +14
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
The following error variants were large enough to trip Clippy's `result_large_err` lint: - RenderPassCompatibilityError::IncompatibleColorAttachment - CreateShaderModuleError::Validation Large error types are a problem, because they make the `Result` type large, requiring the program to copy around large numbers of bytes even in the success case. Since the failure case is rare, it's usually not a problem to just heap-allocate the contents to keep the `Ok` case small.
694eb09
to
8558a40
Compare
This depends on #3226. |
8558a40
to
6ad7c42
Compare
We actually expect to update Firefox to 1.64 very soon, so this PR needs to be amended. We'd very much like to keep all the workspace inheritance changes. |
We don't need this much. |
Firefox is still using an MSRV of 1.63, and wgpu currently uses 1.65.
The 1.64->1.65 jump is from #3184, which I merged. Egg on my face.
The 1.63->1.64 jump is from #3107.
We should have a comment in the top-level Cargo.toml about this, to catch this problem in the future.
Checklist
cargo clippy
.RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown
if applicable.Connections
Link to the issues addressed by this PR, or dependent PRs in other repositories
Description
Describe what problem this is solving, and how it's solved.
Testing
Explain how this change is tested.