You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given how many lints are currently broken for code inside macros, and how many lints have been so over the years, I think it should be a requirement for new lints to at least contain one test that tries to break the lint when used inside a macro. I believe most issues could have been caught by just remembering that macros exists when testing a new lint.
The text was updated successfully, but these errors were encountered:
Also, I am not suggesting that new lints or updated lints should "work" on macros or generics. The only thing that I am suggesting is that if they cannot work in these contexts, they should try to detect these and bail out silently instead of displaying false positives.
gnzlbg
changed the title
require macro testcases for new lints and lints updated
require macro and generic testcases for new lints and lint updates
Apr 17, 2019
Given how many lints are currently broken for code inside macros, and how many lints have been so over the years, I think it should be a requirement for new lints to at least contain one test that tries to break the lint when used inside a macro. I believe most issues could have been caught by just remembering that macros exists when testing a new lint.
The text was updated successfully, but these errors were encountered: