-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce IterableMapEntryExtension
for use with Map.entries
.
#715
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
name: collection | ||
version: 1.19.1 | ||
version: 1.19.1-wip | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should be 1.20.0, unless 1.19.0 hasn't been released yet. |
||
description: >- | ||
Collections and utilities functions and classes related to collections. | ||
repository: https://github.com/dart-lang/core/tree/main/pkgs/collection | ||
|
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Too bad
where
is taken, so it can't bewhere({bool Function(K)? key, bool Function(V)? value})
)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I feel the same with
.map
.But I wouldn't make
where({bool Function(K)? key, bool Function(V)? value})
.I would make:
where(bool Function(K, V) test)
, ignoring a parameter in a closure is not that bad.Maybe, we should consider adding:
wherePair(bool Function(K, V) test)
mapPair<T>(T Function(K, V) toElement)
We could consider adding such extension methods to:
Iterable<MapEntry<K, V>>
, and,Iterable<(A, B)>
.But that seems outside the scope of this PR.
And it's entirely possible that a language feature providing pattern matching in the signature of a closure is better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe
whereEntry
/mapEntry
/anyEntry
/everyEntry
with anX Function(K, V)
argument. (Don't say "pair", it's not — just — a pair! It's a key-and-value.)Some of those (not
whereEntry
) could be extensions toMap<K,V>
too. (Not saying they should, but they could.)