Stop setting current index local which is nonexistent in ValueTuple deserializer #1280
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
jnm2
commented
Jun 13, 2019
|
@mgravell The check that failed (the WIP check) is saying that it needs someone with StackExchange org admin permissions to accept new permissions. |
|
Thanks for resolving so promptly - merged. |
|
@mgravell Using the new prerelease, everything seems to be working as anticipated. |
rhubley
pushed a commit
to rhubley/Dapper
that referenced
this pull request
Jan 29, 2020
…eserializer (DapperLib#1280) * String and byte[] tuple elements cause InvalidProgramException * Stop setting current index local which is nonexistent in ValueTuple deserializer
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.
Fixes #1279, a bug introduced in #1242.
@mgravell I'm sorry I broke master. Hopefully the fix is super easy to review.