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

"forget", leading to confusion? #34

Open
elshize opened this issue Mar 27, 2020 · 0 comments
Open

"forget", leading to confusion? #34

elshize opened this issue Mar 27, 2020 · 0 comments

Comments

@elshize
Copy link

elshize commented Mar 27, 2020

I think that the following is missing a comma to be correctly understood in Memory management section:

In particular, using forget may result in not releasing critical resources leading to deadlocks or not erasing sensitive data from the memory. That is why, forget is unsecure.

As far as I understand, "leading to deadlocks refers to "not releasing critical resources", right?
I think, in order to make it clearer, it should be (notice two additional commas):

In particular, using forget may result in not releasing critical resources, leading to deadlocks, or not erasing sensitive data from the memory. That is why, forget is unsecure.

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