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
In LazyList, strict operations have the following description:
It contains both “Note: Even when applied to a view or a lazy collection it will always force the elements.” and “This method evaluates all elements of the collection.”, which are redundant, IMO.
Some operations have the following comment:
“This method preserves laziness; elements are only evaluated individually as needed.” But this note is not present in the View operations.
We should use only one way to document whether an operation is strict or non-strict, and in case an operation is “mostly lazy” (e.g., takeRight) we should clearly document what will be evaluated and when.
we could potentially re-define whatever variable produces "Note: Even when applied to a view or a lazy collection it will always force the elements." to an empty string? either that or all the LazyList methods need to duplicate their parent scaladocs, which seems un-ideal.
Activity
NthPortal commentedon Apr 23, 2019
we could potentially re-define whatever variable produces "Note: Even when applied to a view or a lazy collection it will always force the elements." to an empty string? either that or all the
LazyList
methods need to duplicate their parent scaladocs, which seems un-ideal.julienrf commentedon Apr 24, 2019
Yes, we can probably use a variable for that.