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

Warn During Compilation if a Context Variable is Set and not Seen in an init() #12

Open
MTrop opened this issue Aug 24, 2018 · 1 comment
Labels
enhancement Nice-to-haves and things that can actually help current behavior. low priority Bugs labeled this are not considered the same priority as regular bugs - user-created rare issues.

Comments

@MTrop
Copy link
Member

MTrop commented Aug 24, 2018

Decent enhancement: if a context variable is being set anywhere, but it was never initialized via init() on that context, the compiler should warn the user so.

These warnings, though, due to the nature of the compiler, will need to be output near the end of compilation.

@MTrop MTrop added the enhancement Nice-to-haves and things that can actually help current behavior. label Aug 24, 2018
@MTrop
Copy link
Member Author

MTrop commented Sep 18, 2018

On second thought this may be way more difficult to do in static analysis. At runtime this is catchable, but it would not be ideal.

Shifting to low priority - this may not even be a huge issue.

@MTrop MTrop added the low priority Bugs labeled this are not considered the same priority as regular bugs - user-created rare issues. label Sep 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Nice-to-haves and things that can actually help current behavior. low priority Bugs labeled this are not considered the same priority as regular bugs - user-created rare issues.
Development

No branches or pull requests

1 participant