Print allocations on --builddir
#109
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elliotgoodrich
force-pushed
the
print-allocations-on-builddir
branch
2 times, most recently
from
bc2eaf5 to
ee453a2
Compare
Standardize how we exit `main` through the `leave` function so that we can make sure to print out our memory stats on every path. To make sure we call `leave` we can decorate `main` as `[[noreturn]]`.
elliotgoodrich
force-pushed
the
print-allocations-on-builddir
branch
from
ee453a2 to
b249dce
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Standardize how we exit
mainthrough theleavefunction so that wecan make sure to print out our memory stats on every path. To make sure
we call
leavewe can decoratemainas[[noreturn]].