What mantra? I think this maintainer is doing the right thing here by trying to understand why this fix works.
You should always attempt to address the root cause of an issue instead of slapping band aid patches onto everything.
To me it looks like the maintainer is trying to find out what exactly is wrong. “this doesn’t happen in our C implementation” implies that there’s something wrong with the rust code specifically.
I guess that’s meant to be 2025 since the graph is projected? Pretty funky screw up though.
FYI, this is from 2015 and was deprecated around rust v1.0 release. It’s not a current issue.
I’m not sure if the rules are different with macros, I’ve never written one but this lint is generally caused because you set a var to a value and then overwrite that value before you use it. e.g.
let mut a = 1; a = 2; println!(“{}”, a);
This will throw the same warning because 1 is never used, this could’ve just been:
let a = 2; println!(“{}”, a);
So first I’d double check that I NEED last at all. Maybe try:
cargo clippy
See if it can tell you how to fix it.
If that doesn’t work, it’s sometimes necessary to skip certain lints. E.g. if you make a library, most of the code will be flagged as dead code because it isn’t used and you can use an #[allow(dead_code)] to stop the linter warning. You might be able to use #[allow(this_linting_rule)].
Hope something here helps.
In that case, this is also a yes.
I’m a developer working for a SaaS company and you didn’t NEED a degree to get hired but it sure was a “nice to have.”
Something I’ve always found funny about the “AI will replace programmers soon” is that this means AI’s can create AI’s and isn’t this basically the end of the economy?
Every office worker is out of a job just like that and labourers only have as long as it takes to sort out the robot bodies then everyone is out of a job.
You thought the great recession was bad? You ain’t seen nothing!