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

Non-ephemeral values analyzer #19

Open
bjorg opened this issue Feb 29, 2016 · 0 comments
Open

Non-ephemeral values analyzer #19

bjorg opened this issue Feb 29, 2016 · 0 comments

Comments

@bjorg
Copy link
Contributor

bjorg commented Feb 29, 2016

For some types, it would be helpful to make sure that they are always used in some capacity. Task comes to mind when returned by an async method. Without using await, the called method will never run passed the first async operation. I use the term "non-ephemeral" to indicate that these values cannot be simply forgotten (i.e. they must be used at least once). "Linear" is a similar concept, but is further restricted by the notion that values must be used exactly once.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant