This issue is only as a note to remember. We have not exposed nilM yet.
before action Stream.nil can be used in place of nilM.
We could express before in terms of nilM too (before action xs = nilM action <> xs) but the advantage of using before is that it can fully fuse whenever possible.
Is there a reason to not use nilM?
Too many options lead to confusion. If before action nil and nilM are exactly the same, we might as well remove nilM.
This issue is only as a note to remember. We have not exposed
nilM
yet.before action Stream.nil
can be used in place ofnilM
.We could express
before
in terms ofnilM
too (before action xs = nilM action <> xs
) but the advantage of usingbefore
is that it can fully fuse whenever possible.