Skip to content
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

Fix issue #135 use StartImmediateAsTask instead of StartAsTask to prevent a thread hop #191

Merged
merged 2 commits into from
Nov 4, 2023

Conversation

abelbraaksma
Copy link
Member

Fixes #135

This brings our task-like behavior in line with the similar change in F# itself, see dotnet/fsharp#14499 (and dotnet/fsharp#14490.

We should probably have a look at these tests (dotnet/fsharp@4054701) and add some of these here as well to ensure we are properly propagating exceptions etc.

@abelbraaksma abelbraaksma force-pushed the fix-135-use-start-immediate-as-tsk branch from 9624ced to 57b742d Compare November 4, 2023 23:43
@abelbraaksma abelbraaksma merged commit 6cee5f4 into main Nov 4, 2023
6 checks passed
@abelbraaksma abelbraaksma deleted the fix-135-use-start-immediate-as-tsk branch November 4, 2023 23:56
@abelbraaksma abelbraaksma added performance Performance questions, improvements and fixes topic: taskseq-ce Related to the taskseq computation expression builders or overloads labels Dec 24, 2023
@abelbraaksma abelbraaksma added this to the v0.4.0 milestone Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Performance questions, improvements and fixes topic: taskseq-ce Related to the taskseq computation expression builders or overloads
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider StartImmediateAsTask instead of StartAsTask to prevent a thread hop
1 participant