Fix parameter name conflict when compiling for .NET Framework 4.6.2 - #65
Merged
momo-the-monster merged 1 commit intoJun 27, 2026
Conversation
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
momo-the-monster
approved these changes
Jun 27, 2026
momo-the-monster
left a comment
momo-the-monster
left a comment
Contributor
There was a problem hiding this comment.
Thanks for this fix! Sorry it took so long to approve, just making my way back to this repo now.
Contributor
|
fixes #67 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Compilation for target .NET Framework 4.6.2 fails due to a parameter name within a lambda already being defined in the surrounding scope.
This PR renames this parameter from "p" to "sp" to avoid this conflict.