Deprecate taskSeq<_>
in favor of TaskSeq<_>
#187
Merged
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.
Similar to have the
Async<_>
andAsyncSeq<_>
type aliases work, we should use the Principle of Least Surprise and do the same.taskSeq { do! ... }
IAsyncEnumerable<_>
, in other words, the output of the computation expression and the building block for basically all functions in this library.The gist of this change is just that this:
becomes
This follows from suggestions made in other issues, but I can't find it readily.
We will keep
taskSeq<_>
around, but it will raise FS0044, a deprecation warning. People can use it just fine by ignoring the warning