Ragged mapping #2314
Closed
Ragged mapping #2314
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
|
I believe there's no test of ragged mapping without this being merged @dnjohnstone? #2391 nearly introduced a bug that would have broken it, I only spotted it by accident since there was no ragged test. |
|
Since #1497 is nearly done @dnjohnstone can this be closed? |
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.
I've pulled out some ragged mapping bug fixes that were wrapped up in #1497
@ericpre wrote these - but I couldn't figure out how to separate them out and preserve authorship. Are you ok with these being included like this for a patch release?