-
Notifications
You must be signed in to change notification settings - Fork 54
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
Analyze unused or undefined table fields #39
Comments
This would be an interesting feature to have it it really worked, but I am skeptical whether it can be implemented robustly enough to be anything more than a giant pile of false positives. Tables get passed around in all sorts of ways (as modules), passed to different scopes, copied to new structures, accessed by meta-methods and raw accessors, serialized, the number of keys in a table can be relevant without direct access to a specific key, etc. Understanding when a field was really used or unused might be hard to implement. |
I can do this, any comments on the idea?
The text was updated successfully, but these errors were encountered: