Skip to content
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

Refine the bounds of the Tuple.Filter type lambda predicate .. #21286

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

EugeneFlesselle
Copy link
Contributor

to only require it be defined on the elements of the tuple.

This is one of the ongoing proposed tuple improvements, addressing #19175.

As carefully pointed out by @sjrd, this is a potential breaking change.
See tests/neg/tuple-filter-compat.scala for an example.

This is not an unprecedented change however, the analogous improvements were made to Tuple.{Map, FlatMap} in 28a695e.

I guess this should be discussed, and decided whether or not to merge, by the core team.

@EugeneFlesselle EugeneFlesselle marked this pull request as ready for review July 29, 2024 13:34
@EugeneFlesselle EugeneFlesselle requested a review from sjrd November 6, 2024 15:54
@EugeneFlesselle EugeneFlesselle enabled auto-merge (rebase) November 6, 2024 15:54
to only require it be defined on the elements of the tuple.

This is one of the ongoing proposed tuple improvements, addressing scala#19175.

As carefully pointed out by @sjrd, this _is_ a potential breaking change.
See tests/neg/tuple-filter-compat.scala for an example.

This is not an unprecedented change however,
the analogous improvements were made to `Tuple.{Map, FlatMap}` in 28a695e.
@EugeneFlesselle EugeneFlesselle merged commit a1d7f5e into scala:main Nov 11, 2024
29 checks passed
@EugeneFlesselle EugeneFlesselle deleted the tuples/filter branch November 11, 2024 08:50
@WojciechMazur WojciechMazur added the backport:nominated If we agree to backport this PR, replace this tag with "backport:accepted", otherwise delete it. label Nov 11, 2024
@WojciechMazur WojciechMazur added this to the 3.6.2 milestone Nov 11, 2024
@tgodzik tgodzik added the release-notes Should be mentioned in the release notes label Nov 18, 2024
@WojciechMazur WojciechMazur added backport:accepted This PR needs to be backported, once it's been backported replace this tag by "backport:done" and removed backport:nominated If we agree to backport this PR, replace this tag with "backport:accepted", otherwise delete it. labels Nov 18, 2024
WojciechMazur added a commit that referenced this pull request Nov 18, 2024
…te .." to 3.6 (#21960)

Backports #21286 to the 3.6.2.

PR submitted by the release tooling.
[skip ci]
@WojciechMazur WojciechMazur added backport:done This PR was successfully backported. and removed backport:accepted This PR needs to be backported, once it's been backported replace this tag by "backport:done" labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:done This PR was successfully backported. release-notes Should be mentioned in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants