Skip to content
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.

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

How is -Wconf supposed to work? #12984

Open
som-snytt opened this issue Apr 10, 2024 · 0 comments · May be fixed by scala/scala#10750
Open

How is -Wconf supposed to work? #12984

som-snytt opened this issue Apr 10, 2024 · 0 comments · May be fixed by scala/scala#10750
Labels

Comments

@som-snytt
Copy link

Questions are not bug reports

What if it's a documentation bug?

I realize that's another question.

Reproduction steps

Scala version: 2.13.13

scalameta/munit#461

to exercise -Wconf:cat=deprecation:s -Xlint and upgrading a project.

Problem

It still warns, even with -Wconf:any:s.

If I junkify the config, it tells me

[error] Failed to parse `-Wconf` configuration: List(cat=deprecation:w, junk:s, cat=unchecked:w, cat=feature:w, cat=deprecation:ws, cat=feature:ws, cat=optimizer:ws)
[error] unknown filter: junk

Ah, I thought a plugin was prepending to the config, but I just realized that Xlint sets deprecation which sets -Wconf.

But what if I only want to see some deprecations?

That is my third and final question.

Besides documenting the behavior, under -verbose it could echo settings or explain what's going on when a filter matches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant