lolbinarycat
lolbinarycat
> I've ran lintcheck on top 200 popular crate with this lint, unfortunately I didn't see any thing related, putting it in 'nursery' is just further limiting it's useages, so...
also, if the argument variable only appears in autoreferencing method calls (like in the current tests) it should be possible.
> Hmm I see. we can fix that by adding a `&` to `filter`'s signature if it's `Copy`, check `clippy_utils::ty::is_copy`. Otherwise it should be non-applicable if it's `!Copy` yet warn-by-default...
i've kinda abandoned it since it seems like there might already be a lint for this?
It seems like it would still be fine on linux, no? this pattern is quite common in shell scripts.
At the very least we should add an `is_weak` method to `ETag` so this can be mitigated in the meantime.
somewhat related, there's no way to get the string of an etag so i can nicely print it in error messages.
Hm, perhaps `CrosstermBackend::new` and `Terminal::new` should mention they don't install the panic hook, unlike `init`? I just checked an the misbehaving application isn't using `init`. At the same time I...
One thing that *could* be done would be to expose `set_panic_hook`, although it would probably need a bit better documentation and possibly a more descriptive name in that case.
yeah i see that. the actual problem is that the rules for temporary lifetime extension are obfuscated and incomprehensible. and also that `rust-analyzer` doesn't catch these errors, leading me to...