You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
853: Clippy warnings on nightly + first cargo-deny entry r=Bromeon a=Bromeon
### clippy warnings
The first commit fixes warnings on nightly:
```rs
Checking gdnative-derive v0.9.3 (/home/runner/work/godot-rust/godot-rust/gdnative-derive)
error: methods called `from_*` usually take no `self`
--> gdnative-derive/src/variant/repr.rs:174:9
|
174 | &self,
| ^^^^^
|
= note: `-D clippy::wrong-self-convention` implied by `-D clippy::style`
= help: consider choosing a less ambiguous name
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#wrong_self_convention
error: methods called `from_*` usually take no `self`
--> gdnative-derive/src/variant/repr.rs:330:21
|
330 | fn from_variant(&self, variant: &TokenStream2) -> TokenStream2 {
| ^^^^^
|
= help: consider choosing a less ambiguous name
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#wrong_self_convention
```
---
### cargo-deny entry
After reading [this Reddit post](https://www.reddit.com/r/rust/comments/sdgcg9/unsoundness_in_owning_ref), the `owning_ref` crate seemed to be a good candidate for cargo-deny. First, it hasn't been maintained in two years, and second, there is [known unsoundness](https://github.com/noamtashma/owning-ref-unsoundness) but it's not marked in any CVE database.
I'm not suggesting we go hunt down crates now, but if people come across other problematic crates, let's add them. That doesn't mean there will be a strict ban on such crates forever, but it means adding a potentially problematic dependency is a concious, opt-in process.
bors try
Co-authored-by: Jan Haller <[email protected]>
0 commit comments