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

False positive "unused explicit parameter" warning when class has var parameter #16955

Closed
SethTisue opened this issue Feb 18, 2023 · 0 comments · Fixed by #16957
Closed

False positive "unused explicit parameter" warning when class has var parameter #16955

SethTisue opened this issue Feb 18, 2023 · 0 comments · Fixed by #16957
Labels
area:linting Linting warnings enabled with -W or -Xlint itype:bug stat:needs triage Every issue needs to have an "area" and "itype" label
Milestone

Comments

@SethTisue
Copy link
Member

SethTisue commented Feb 18, 2023

//> using scala "3.nightly"
//> using option "-Wunused:all"

class S(var r: String)
[warn] ./S.scala:4:9: unused explicit parameter
[warn] class S(var r: String)
[warn]         ^

this is with the current nightly (Scala 3.3.1-RC1-bin-20230216-2507577-NIGHTLY). same with 3.3.0-RC3.

@SethTisue SethTisue added itype:bug stat:needs triage Every issue needs to have an "area" and "itype" label area:linting Linting warnings enabled with -W or -Xlint labels Feb 18, 2023
szymon-rd added a commit that referenced this issue Feb 18, 2023
@szymon-rd Fixes #16955

- Do not report parameter of accessors
- Update test suit
@Kordyjan Kordyjan modified the milestones: 3.3.1, 3.3.0 Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:linting Linting warnings enabled with -W or -Xlint itype:bug stat:needs triage Every issue needs to have an "area" and "itype" label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants