We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
iterable[T]
toSeq
goal: introduce a type for called iterators instead of being treated as untyped (which will make elementType and toSeq well typed), which would resolve some other issues: nim-lang/RFCs#512 nim-lang#9219 nim-lang#13595 nim-lang#14148 nim-lang#16545 and sidestep nim-lang#14778 and reduce cases where we hit nim-lang#14827
elementType
Note: concepts aren't powerful enough to express that, so type Iterable[T] = concept can't work
type Iterable[T] = concept
related
concepts
=> PR nim-lang#17196
The text was updated successfully, but these errors were encountered:
toSeq(bar())
bar()
No branches or pull requests
goal: introduce a type for called iterators instead of being treated as untyped (which will make
elementType
andtoSeq
well typed), which would resolve some other issues:nim-lang/RFCs#512
nim-lang#9219
nim-lang#13595
nim-lang#14148
nim-lang#16545
and sidestep nim-lang#14778
and reduce cases where we hit nim-lang#14827
Note: concepts aren't powerful enough to express that, so
type Iterable[T] = concept
can't worklinks
related
concepts
nim-lang/Nim#12048 (enableif, allowing to express arbitrary constraints in routine signatures)I've implemnted this in fact, see every symbol becomes 1st class; defines 0-cost lambda and aliases; generics/iterators/templates/etc can be passed to any routine nim-lang/Nim#11992 (comment)
implementation
=> PR nim-lang#17196
The text was updated successfully, but these errors were encountered: