You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There doesn't seem to be a test suite. I would recommend adding, at least:
Modules implementing the entire non-internal streaming API using FreeT instead of Stream. I think these might as well be exposed, so users can play with them.
Tests verifying that Stream operations behave the same as their FreeT equivalents. See my old SO question How can I test functions polymorphic over applicatives for some ideas about being arbitrary. In this case, I suspect we want to use functors built from algebraic bits (Sum, Product, Compose, Identity, Const) for f parameters, and free monads over such functors for m parameters.
The text was updated successfully, but these errors were encountered:
I like this idea a lot. It seems like the best way to verify that the functions provided by streaming are correct. Rather than sticking the new modules in streaming though (which would cause the library to incur a dependency on free for something that very few end users would need), I would rather just have a streaming-free library that provides them. Then, the test suite for streaming could depend on this.
On Sep 13, 2017 10:47 AM, "Andrew Martin" ***@***.***> wrote:
I like this idea a lot. It seems like the best way to verify that the
functions provided by streaming are correct. Rather than sticking the new
modules in streaming though (which would cause the library to incur a
dependency on free for something that very few end users would need), I
would rather just have a streaming-free library that provides them. Then,
the test suite for streaming could depend on this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABzi_TQpZSFPCU4fOxnQ_1LdZROQRRHcks5sh-sHgaJpZM4PWH0O>
.
Original issue by @treeowl:
The text was updated successfully, but these errors were encountered: