Skip to content

Analyzer should report issues with @optionalTypeArgs #34260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
srawlins opened this issue Aug 25, 2018 · 1 comment
Closed

Analyzer should report issues with @optionalTypeArgs #34260

srawlins opened this issue Aug 25, 2018 · 1 comment
Labels
legacy-area-analyzer Use area-devexp instead. strict-analysis-needed Mark issues where strict-raw-types, strict-inference and similar analysis options were helpful

Comments

@srawlins
Copy link
Member

As per optionalTypeArg's docs, the analyzer should suppress warnings that otherwise require type arguments to be provided for a class.

But what warnings would these be? Looks like #32538 at minimum (maybe other implicit-dynamic warnings).
@mit-mit mit-mit added the legacy-area-analyzer Use area-devexp instead. label Aug 29, 2018
@srawlins
Copy link
Member Author

This is currently respected by strict-raw-types: true and strict-inference: true.

@eernstg eernstg added the strict-analysis-needed Mark issues where strict-raw-types, strict-inference and similar analysis options were helpful label Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
legacy-area-analyzer Use area-devexp instead. strict-analysis-needed Mark issues where strict-raw-types, strict-inference and similar analysis options were helpful
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@srawlins @eernstg @mit-mit