Skip to content

seperate Into<Iterator<t>> and Iterable<T>, like in rust #1467

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
Open
alex-s168 opened this issue May 2, 2025 · 1 comment
Open

seperate Into<Iterator<t>> and Iterable<T>, like in rust #1467

alex-s168 opened this issue May 2, 2025 · 1 comment
Assignees
@alex-s168
Labels
enhancement New feature or request stdlib

Comments

@alex-s168
Copy link
Collaborator

alex-s168 commented May 2, 2025 •
edited
Loading

in the future, the compiler should auto-optimize Iterable<T> to Into<Iterator<t>> for owned types
@alex-s168 alex-s168 added enhancement New feature or request stdlib labels May 2, 2025
@alex-s168 alex-s168 self-assigned this May 2, 2025
@alex-s168 alex-s168 mentioned this issue May 2, 2025
Closed
@andrew-johnson-4
Copy link
Collaborator

depends on Into types: #1104

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

@alex-s168 alex-s168

Labels
enhancement New feature or request stdlib
Projects
stdlib feature tracking
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alex-s168 @andrew-johnson-4