Skip to content

Conversation

som-snytt
Copy link
Contributor

@som-snytt som-snytt commented Sep 23, 2025

Fixes #23967

It needs more mechanism for compiletime ops that are inlined but not Inlined.

@som-snytt som-snytt force-pushed the issue/21805-compile-time branch from 2ac247e to b0cd466 Compare October 15, 2025 15:21
@som-snytt som-snytt marked this pull request as ready for review October 15, 2025 15:22
@som-snytt
Copy link
Contributor Author

som-snytt commented Oct 15, 2025

Another idea is that using the compile time facility makes all enclosing imports "used"; that results in false negatives instead of false positives.

Edit: in fact, all the warnings are nullified by the facility. We can't detect the erased usage of typeChecks, so just witnessing the import turns off linting the compilation unit.

The ultimate goal is to represent the typeChecks code as Inlined (by some convention).

@som-snytt som-snytt changed the title Ignore compiletime.testing for warning Ignore warnings when compiletime.testing is imported Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wunused: False positive for compiletime.testing.typeCheckErrors

1 participant