-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create cats.data.NonEmptyStream? #1089
Comments
This continues work started by @WarFox in typelevel#1120 (see [this comment](typelevel#1120 (comment))). At this point, I have left `OneAnd` in place. However, I think that after merging this we may want to delete it. In practice it's pretty awkward to use and sometimes prevents performant operations. See also typelevel#1089.
I'm at the point where I would like to have NonEmptyStream currently. I have a Edit: In retrospect, since I know I'm going to iterate through the entire |
@wjlow or you can use OneAnd right? https://github.com/typelevel/cats/blob/master/core/src/main/scala/cats/data/OneAnd.scala |
Yes, thanks! |
Once #1087 and #1088 have been completed, I think that we should probably drop
OneAnd
from cats. At that point, I think thatNonEmptyStream
would be the only data structure referencing it. We can probably dropNonEmptyStream
at that point, but I created this issue to let people weigh on ifNonEmptyStream
is something that they would really want in cats. I suspect that it's not really used.The text was updated successfully, but these errors were encountered: