Multiple fixes related to Dictionary.Keys bug #1786
Merged
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
…the value should not be disposed
…eneric arguments as long as there is no ambiguity
|
Could you split part 2 out into a separate PR for discussion and add a few tests? |
|
Do you have any specific concerns? The reason I made the quality of life change is to use it in |
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.
What does this implement/fix? Explain your changes.
This has individual commits for:
Dictionary.Keysto be confused with theDictionaryitselfGeneric.IEnumerable(obj), which previously required the generic type argument to be specified. E.g.Generic.IEnumerable[String](obj)was requiredDoes this close any currently open issues?
fixes #1785
Checklist
Check all those that are applicable and complete.
CHANGELOG@Martin-Molinero