-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
overload resolution (with typed and untyped) doesn't work with iterators #9219
Labels
Comments
Can you provide an example to this issue? At the moment I don't know how what code you would want to compile and what it should mean. |
[EDIT]
|
timotheecour
changed the title
overload resolution should work with untyped and typed overloads
overload resolution (with typed and untyped) doesn't work with iterators
Nov 1, 2018
This was referenced Jun 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[EDIT]
code below gives CT error, it should work instead.
this would fix Exporting a
toSeq
overload messes up iterator visibility RFCs#512unlike what was said in Exporting a
toSeq
overload messes up iterator visibility RFCs#512 I don't see a way to have atoSeq(s: typed)
that works with inline iterators.See also my PR #8711 to have a universal toSeq: the
untyped
case is still needed to allow for inline iterators egtoSeq(keys(myTable))
EDIT note
this could either be fixed by nim-lang/RFCs#60
The text was updated successfully, but these errors were encountered: