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.

Sign up for GitHub

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

Jump to bottom

It would be nice to have a Top operator that would merge OrderBy and Take #103

Open

GoogleCodeExporter opened this issue Dec 3, 2015 · 1 comment

Labels

auto-migrated Type-Enhancement

GoogleCodeExporter commented Dec 3, 2015

This same argument for Max and Min could be applied to this operator. The main 
benefit would be performance, but I think it actually might be more readable. 
Without the requirement of sorting the entire list, you move from an average 
case of O(n log n)for an optimal sorting algorithm to O(n) for an optimal 
selection algorithm.

Original issue reported on code.google.com by Pope...@gmail.com on 27 May 2015 at 9:49

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added auto-migrated Type-Enhancement labels

Author

GoogleCodeExporter commented Dec 3, 2015

This issue has been migrated to:
https://github.com/MoreLINQ/morelinq/issues/103
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 21 Aug 2015 at 6:56

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment