Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Relegate the on-close for emergencies #1175
Relegate the on-close for emergencies #1175
Changes from 3 commits
b39c768
0495049
50799bb
d300ea6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused about this line. Why do we need to "trigger emergency file-close"? IIUC we've just cleaned things up above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its going to get triggered eventually. Might as well trigger it now, when I know it is an no-op.
I guess I'm vague uncomfortable with this split: here on line 63 we close
fout
, let's say its 24. My understanding of how anonymous functions work is that the onCleanup still has "24" hardcoded in it (it has no ideafout
has been replaces with[]
).Some other
fopen
call later reuses 24.Now our ticking timebomb onCleanup goes off and closes that 24. I don't know if that can really happen but the idea that it might means I don't like that onCleanup lying around. Let it go off right now while its harmless.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe I should have a comment that gives that idea:
% trigger while we know it is a no-op
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, this should make things clearer
This file was deleted.