Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Compilation should fail when `@silent` does not suppress anything
See original GitHub issueCurrently it seems like @silent can be added anywhere, even if it’s not needed. This is particularly bothersome when it’s applied to classes; a code change could fix the initial warning that’s being ignored, but leave @silent in place, opening up accidental regression on further code changes.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
JS compilation error causes silent failure to compile unrelated ...
We've run into an issue where use of Math.abs is causing the build task to fail silently, generating only a subset of our...
Read more >Suppress messages in make clean (Makefile silent remove)
SILENT ) suppresses just anything. Especially the "nothing to be done" and "up to date" messages can be a pain. There is no...
Read more >Tricks For Silencing Make (automake) - GNU.org
21.2 Standard and generic ways to silence Make. Here we describe some common idioms/tricks to obtain a quieter make output, with their relative...
Read more >PHP 8.0: @ Error Suppression operator does not silent fatal ...
With this change in PHP 8.0, the @ operator might not suppress all the errors. This is a desired result, because all the...
Read more >Suppress compiler warnings - Visual Studio - Microsoft Learn
In the Suppress warnings or Suppress specific warnings box, specify the error codes of the warnings that you want to suppress, separated by ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
fwiw, breaking existing projects seems okay to me here. the existing projects are likely to want to remove those stale annotations
Fixed in 1.4.0