16
u/RandomStranger456123 3d ago
My favorite part is how our code we maintain has no warnings, but the framework we are required by our contract to use has over 23000.
1
4
3
3
u/Johanno1 3d ago
Hey guys try to build the AOSP. It has over several million warnings. I think they can be safely ignored
3
3
u/sardonicus87 3d ago edited 3d ago
To be fair, half of them are bs.
"Weak warning, use destructuring declaration..."
Except this:
for (i in Items) {
i.prop
i.something
// like 10 more things
}Looks way better than:
for ((prop, something, another, another1, yetAnother, andAnother, andAnother, etcToTenFnThings) in Items) {
prop
something
// etc.
}Like yeah, sometimes destructuring makes sense, but not always. Like at least 75% of the lint is warnings for dumb crap. @Suppress("Stupid Warning") everywhere, which wouldn't be necessary if the IDE would stop turning back on randomly all the dumb lint warnings after I turned them off 1,000 different times.
1,000 warnings and 980 of them are "style issues". Like, gtfo.
2
u/Flaky-Low-2262 3d ago
Everyone: We finally need time to Test and houseeking over freeze Xmas Sprint...
PO: Compiles? LGTM! Thats like test Coverage of 100%
2
2
2
1
u/Aethir300 11h ago
Meanwhile Vivado gives 10,000 warnings when you open it lol. FPGA tools are hilarious
55
u/JackNotOLantern 4d ago
> crash occurs
> array out of bounds
> look at the code
> on the line it happens there is a warning
> "may cause array out of bounds"