- Notifications
You must be signed in to change notification settings - Fork5.1k
Remove Current interface call in IteratorSelectIterator#99344
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
By returning `Iterator<>` from GetEnumerator, strongly-typed callers (such as those in IteratorSelectIterator) can bind to the non-virtual Current member, saving an interface/virtual call. The interface dispatch to MoveNext also becomes virtual for such callers.
ghost commentedMar 6, 2024
Tagging subscribers to this area: @dotnet/area-system-linq Issue DetailsBy returning
|
By returning
Iterator<>
from GetEnumerator, strongly-typed callers (such as those in IteratorSelectIterator) can bind to the non-virtual Current member, saving an interface/virtual call. The interface dispatch to MoveNext also becomes virtual for such callers.