-
Notifications
You must be signed in to change notification settings - Fork 136
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
Migrate to our Standard CI #437
Conversation
|
||
- name: cargo clippy (wasm) | ||
run: cargo clippy --all-targets --target wasm32-unknown-unknown -- -D warnings | ||
env: |
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.
This is an improvement!
// TODO: This is a public method, which means it definitely is not | ||
// "dead code". However, rustc seems insitent that it is, and so to not | ||
// block forward progress, I shall humour it | ||
#[allow(dead_code)] |
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 can't prioritise debugging and resolving this, so think we should land this without that
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.
Yeah I honestly think it's a bug in Rust, the error warning doesn't make sense to me as the type BindType
is clearly public...
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.
Going towards a more unified CI makes sense. LGTM, thanks :)
// TODO: This is a public method, which means it definitely is not | ||
// "dead code". However, rustc seems insitent that it is, and so to not | ||
// block forward progress, I shall humour it | ||
#[allow(dead_code)] |
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.
Yeah I honestly think it's a bug in Rust, the error warning doesn't make sense to me as the type BindType
is clearly public...
* Headless: Pass in the use_cpu arugment * Move to our standard CI * "Resolve" the warnings detected by CI * Fix the doc warnings
See also linebender/peniko#21
I haven't added an MSRV yet, as we're not at that stage
This also lets the headless example use the
--use-cpu
flag. This isn't currently used in CI - I'm planning to make atests
crate/PR instead