Skip to content

Update documentation for LazyList #11131

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

Closed
1 task done
NthPortal opened this issue Sep 3, 2018 · 5 comments
Closed
1 task done

Update documentation for LazyList #11131

NthPortal opened this issue Sep 3, 2018 · 5 comments

Comments

@NthPortal
Copy link

NthPortal commented Sep 3, 2018

Update scaladocs for LazyList, following up on scala/collection-strawman#367, scala/scala#7000, #11307, scala/scala#7558, and probably others.


A non-exhaustive list of things to document:

  • which methods preserve laziness, and to what degree
@NthPortal NthPortal added the docs label Sep 3, 2018
@NthPortal NthPortal added this to the 2.13.0-RC1 milestone Sep 3, 2018
@NthPortal
Copy link
Author

I would love it if someone else volunteered to take this on - I would like to focus on ensuring that LazyList is properly lazy.

@NthPortal
Copy link
Author

NthPortal commented Feb 21, 2019

It would be really nice to have this done by 2.13.0 final release. I guess I'll grab it for now and try to get it done, unless anyone else pipes up.

@NthPortal
Copy link
Author

Reopening for some followup to scala/scala#7842

@NthPortal NthPortal reopened this Mar 22, 2019
@NthPortal NthPortal removed their assignment Mar 22, 2019
@szeiger szeiger modified the milestones: 2.13.1, 2.13.2 Aug 28, 2019
@SethTisue
Copy link
Member

SethTisue commented Feb 6, 2020

scala/scala#7842 was merged. @NthPortal feel free to reopen if you actively intend to make further improvements sometime in the next month or two. otherwise, let's leave it closed, there are lots of things in stdlib that ideally would have better Scaladoc

@SethTisue SethTisue modified the milestones: 2.13.2, 2.13.0 Feb 6, 2020
@NthPortal
Copy link
Author

@SethTisue I have no idea what the intended followup was, so I'm gonna leave it closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants