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
Tracking issue for iter_order_by #64295
Comments
Document the unstable iter_order_by library feature Tracking issue: rust-lang#64295 Follow-up for: rust-lang#62205 References the tracking issue and adds a page to the unstable book for the new unstable `iter_order_by` feature.
Document the unstable iter_order_by library feature Tracking issue: rust-lang#64295 Follow-up for: rust-lang#62205 References the tracking issue and adds a page to the unstable book for the new unstable `iter_order_by` feature.
Document the unstable iter_order_by library feature Tracking issue: rust-lang#64295 Follow-up for: rust-lang#62205 References the tracking issue and adds a page to the unstable book for the new unstable `iter_order_by` feature.
A comment was made on Twitter about whether or not this should be able to use
|
An example usage of this is in rust-analyzer where it's part of its internal |
TrustedLen is an unsafe trait, which I understand is there to catch cases when wrong lengths would result in soundness holes. The size hint is a bit more than a hint -- an iterator that does not adhere to the bounds is considered buggy by size_hint's documentation. I'd place returning false to Is that the only contested point about this interface? If not, what is needed to move this toward stabilization? (If it's user reports: it simplifies code in coap-handler-implementations quite a bit). |
Function should be renamed to related_by, because, in the function we're not checking for equality, rather we're checking for relation between the values of the two iterators. |
Landed in #62205
Public API
Before stabilization:
Open questions
size_hint
as an optimization for equality checking? That means buggy iterators may return incorrect results foreq_by
. We could optimize for just a handful ofTrustedLen
iterators instead.The text was updated successfully, but these errors were encountered: