[do not merge] shrink memory layout of garagedoor to the tight required minimum#1618
Open
samuelgruetter wants to merge 1 commit into
Open
[do not merge] shrink memory layout of garagedoor to the tight required minimum#1618samuelgruetter wants to merge 1 commit into
samuelgruetter wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is just to demo that the end-to-end garagedoor theorem still holds if we shrink the memory requirements to the required minimum. This is a fun experiment to mention in an evaluation section, but I would not merge it, because any future change that increases memory usage, no matter by how little, would break the end-to-end theorem, whereas with the current memory layout, we have some slack, which I think we should keep.