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.

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

Report unused global variables #23

Open
quchen opened this issue May 12, 2016 · 2 comments
Open

Report unused global variables #23

quchen opened this issue May 12, 2016 · 2 comments
Labels
User experience

Comments

@quchen
Copy link
Owner

quchen commented May 12, 2016 •
edited
Loading

  • Warn on unused globals
  • Remove unused bindings so they can be GC'd
@quchen
Copy link
Owner Author

quchen commented May 20, 2016

There is only one scoping rule, and that is that inside a lambda form, the explicit free/bound names and the top-level names are in scope. But bookkeeping over multiple nested closures and lets might be a bit error-prone.

@quchen quchen changed the title Report unused variables Report unused global variables May 27, 2016
@quchen quchen self-assigned this Jul 11, 2016
@quchen
Copy link
Owner Author

quchen commented Jul 11, 2016

WIP in the static-analysis branch

quchen added a commit that referenced this issue Jul 12, 2016
@quchen
Track explicitly and all free variables separately
f68ea66 
Global variables are implicitly free, so this separation (which only
makes a difference in lambda forms) is a step towards #23, since the
global variables are all the free variables that aren't mentioned
explicitly.
@quchen quchen mentioned this issue Aug 9, 2016
Closed
@quchen quchen removed their assignment Jun 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
User experience
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@quchen