-
Notifications
You must be signed in to change notification settings - Fork 2
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
Warn on accessing undefined globals/names #7
Labels
Comments
SquidDev
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
labels
Feb 4, 2020
SquidDev
added a commit
that referenced
this issue
Feb 22, 2020
SquidDev
added
area-linters
Issues relating to linters and code fixers
and removed
documentation
Improvements or additions to documentation
labels
Mar 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Now that #6 is merged, we have a decent way of determining what globals and modules are available in the current context. This should allow us to monitor global and
require
usages, and ensure they are consistent with what one might expect.I'm probably envisaging two warnings here, though they can probably be done with the same linter:
However, it's not clear how to handle external names. We can definitely bake the standard library into illuaminate, but it might be nice to find a better way.
The text was updated successfully, but these errors were encountered: