- Notifications
You must be signed in to change notification settings - Fork3.1k
Make lhs of#::: inLazyList.Deferrer lazier#10819
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:2.13.x
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| "Use the #::: method with a by-name parameter instead; see docs for more info", | ||
| since = "2.13.15" | ||
| ) | ||
| def #:::[B >: A]()(prefix: LazyList[B]): LazyList[B] = prefix lazyAppendedAll l() |
NthPortalJul 27, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
this is a trick I learned from@armanbilge (deliberate fake tag, I don't want to ping) to maintain bincompat but also prevent source collision
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
You can even declare it asprotected[immutable] still that it doesn't appear in the public API at all.
I believe the failure is that they're not forward compatible? but I thought that was supposed to be disabled now? |
hello, nice to see you here!
Not for 2.13.15. Groundwork has been lain for disabling it, perhaps in 2.13.16. |
2.13.16 will be a modest release without bincompat changes, but it appears increasingly likely that we can start accepting this kind of PR for 2.13.17 |
Uh oh!
There was an error while loading.Please reload this page.
not forward compatible