![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…
When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…
Masks don’t only protect from airborne viruses…
Oh, that makes warnings errors and does not mean “ignore errors”. I’m not too familiar with compiler flags. You could do some mental gymnastics to argue that the unused variable causes the compiler to exit and thus the code is not functioning and thus the unused variable is not a warning but an error :^)
I for my part prefer it that way. Makes sure the code stays clean and nobody can just silence the warnings and be done with it. Because why would you accept useless variables that clutter the code in production builds? Imagine coming back after some time and try to understand the code again. At least you have the guarantee the variable is used somehow and not just “hmm, what does this do? … ah, it’s unused”
Unused variable is an error which fails to compile.
And half of them are “curated list of X”
absolute galaxy brain moment
The stalebot is most times useless. The only scenario where I can see use of it is a maintainer waiting for the reporter to add information. But closing issues because no maintainer checked on them? That’s garbage and discourages bug reports.
Why would I want to sync accounts across instances? Isn’t my content automatically federated?
You get a loyalty discount in the second and third year, so do you only pay the full price once.
Might not get a segfault but you sure can get a core dump.
The thing you are thinking about is called TOTP or timed one time password.