Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Closes #6
Types of changes
What types of changes does your code introduce to IcedTasks?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
I implemented both
Async.StartChild
andAsync.StartImmediateAsTask
as described by The BDFN Himself to get a better idea of performance differences between them. I did 3 types of tests:NonAsyncBinds
- These will return synchronously and not yieldAsyncBinds
- These will return asynchronously and yieldAsyncBindsLong
Same asAsyncBinds
but shows that paralleland!
can be beneficial on slower computations.Additionally I added an
applicative_overhead
to compare 10let!
vs 10let! ...and!... and! ...
to see what the overhead is.Take away is
Async.StartImmediateAsTask
seems to out performAsync.StartChild
which is probably due toAsync.StartChild
running the computation on the threadpool.