Similar to have the Async<_> and AsyncSeq<_> type aliases work, we should use the Principle of Least Surprise and do the same.
When people use the camelCased version, it will always refer to the computation expression: taskSeq { do! ... }
When they use the PascalCased version, it will always refer to the asynchronous enumerable type 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:
type taskSeq<'T> = IAsyncEnumerable<'T>
becomes
type TaskSeq<'T> = IAsyncEnumerable<'T>
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
From version 0.4.0 onward, 'TaskSeq<_>' is deprecated in favor of 'TaskSeq<_>'. It will be removed in an upcoming release."
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