Nick Mancuso

>Please consider the last [report](https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/a41bb9e_2024112416/reports/diff/index.html) (always) , Not sure if this is a good policy, especially when we are generating several reports purposefully. If we have some bad/ invalid report,...

> @romani, the checker framework may add the `@Nonnegative` from `javax` as an alias to their annotation in the future update. I will keep track of that so we can...

> Bitset is details of implementation, we should not leak fact that we are limited to Bitset. I agree with this statement, we should create an issue to discuss not...

Please follow the bug report template, in the issue description, as is always requested

I am removing approved label, we still have some work to do in description

@mahfouz72 please do: - order this ticket the same way that we have https://github.com/checkstyle/checkstyle/blob/master/docs/NEW_LANGUAGE_FEATURE_INTEGRATION_PROCESS.md (please always do this) - why ParenPad and NoWhitespaceAfter? A short blurb about why would be...

I am good to approve after: - Similar and Related Tokens, remove: - JavadocType - patterns are not types - RecordComponentnName - we have PatternVariableName - Make section for new...

> > * add a check for if we have an unused pattern variable, that we suggest using an unnamed pattern instead > > I was going to add this...

@rnveach please approve if you are good, I am

> > You may want to consider leaving spots to write in the issue numbers and cross out things as they are completed so we have full recording and accounting...