Skip to content

Improve efficiency of dead code checks #6617

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

Merged
merged 1 commit into from
May 15, 2018

Conversation

retronym
Copy link
Member

@retronym retronym commented May 11, 2018

  • Move the checkDead module out of Typer
  • Use a new bit in ContextMode to track when to suppress
    the warning, rather than maintaining the stack of the
    symbols of enclosing applications
  • Only do any of this when under -Ywarn-dead code

References scala/scala-dev#501

@scala-jenkins scala-jenkins added this to the 2.13.0-M5 milestone May 11, 2018
  - Move the checkDead module out of Typer
  - Use a new bit in ContextMode to track when to suppress
    the warning, rather than maintaining the stack of the
    symbols of enclosing applications
  - Only do any of this when under -Ywarn-dead code

References scala/scala-dev#501
@retronym retronym force-pushed the faster/checkdead branch from f6e3a4e to fc72bbb Compare May 11, 2018 04:34
@retronym
Copy link
Member Author

neg/check-dead.scala is the relevant, existing test.

@SethTisue SethTisue added the performance the need for speed. usually compiler performance, sometimes runtime performance. label May 11, 2018
@retronym retronym requested a review from adriaanm May 15, 2018 12:12
@adriaanm
Copy link
Contributor

Would be nice to factor out the stuff from checkDead to probably a single method or two in context.

@adriaanm adriaanm merged commit be5d304 into scala:2.13.x May 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance the need for speed. usually compiler performance, sometimes runtime performance.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants