Skip to content
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

add max_by_key #408

Merged
3 commits merged into from
Nov 2, 2019
Merged

add max_by_key #408

3 commits merged into from
Nov 2, 2019

Conversation

yjhmelody
Copy link
Contributor

@yjhmelody yjhmelody commented Oct 29, 2019

Copy link
Contributor

@yoshuawuyts yoshuawuyts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. Thanks heaps for this!

@yoshuawuyts
Copy link
Contributor

Oops, I tried resolving a merge conflict but it looks like I may have broken this branch on accident. It should be something minor though. @yjhmelody could you maybe take a look? Apologies for the inconvenience.

@yoshuawuyts
Copy link
Contributor

@yjhmelody we accidentally merged a bad commit and merged fixes to our CI pipeline. Could you perhaps try rebasing again? Thanks!

@yjhmelody yjhmelody force-pushed the stream-max_by_key branch 2 times, most recently from 0d44028 to 0ab8f78 Compare November 2, 2019 03:34
@ghost ghost merged commit 3a2e6d5 into async-rs:master Nov 2, 2019
@yjhmelody yjhmelody deleted the stream-max_by_key branch November 2, 2019 15:34
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants