Skip to content

Conversation

dsyme
Copy link
Contributor

@dsyme dsyme commented Oct 29, 2022

No description provided.

abelbraaksma and others added 26 commits October 26, 2022 02:43
…is, partially fixed

Issue has to do with the MemberwiseClone() for shadowing the enumerator is not enough to reset the necessary states. Furthermore, after this is sorta fixed, the ValueTask that is used to keep the MoveNext boolean gets accessed twice asynchronously, which is not allowed. It also seems that using 'use' on the taskSeq.GetAsyncEnumerator fails by double disposing. This can probably be considered "by design" but should carefully be considered.
…h solves calling MoveNextAsync() multiple times after completion and removes the InvalidStateException
…cessed in lock step, or individually to completion
…w Enumerator, after a full loop through all items
…tors when tasks are yielded, instead of concrete
@abelbraaksma
Copy link
Member

Not sure why the CI doesn't kick off. Is this still needed, btw? I'll see if I can resolve the conflicts.

@abelbraaksma
Copy link
Member

yeah, after merging and fixing the conflicts, there are no changes anymore, so I'll close this out.

@abelbraaksma
Copy link
Member

This was completed in #42, #49, #51.

@abelbraaksma abelbraaksma added bug fix investigation Requires further or deeper investigation labels Oct 29, 2022
@abelbraaksma abelbraaksma added this to the v0.1.0 milestone Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fix investigation Requires further or deeper investigation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants