Remove the is_first_cell/clear_first_cell() mechanism from Mapping. #1353
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
This truly makes the Mapping::InternalDataBase objects stateless: we no longer need to worry about whether we are on the first cell or not.
tamiko
added a commit
that referenced
this pull request
Aug 13, 2015
Remove the is_first_cell/clear_first_cell() mechanism from Mapping.
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.
This truly makes the Mapping::InternalDataBase objects stateless: we no
longer need to worry about whether we are on the first cell or not.
This patch depends on #1339 to be merged first. It implements the
mapping half of #1305 and makes the mapping half of #1335 possible.
In reference to #1198.