Skip to content

Conversation

nicolasstucki
Copy link
Contributor

@nicolasstucki nicolasstucki commented Aug 30, 2023

These methods should not have been stabiliezed in the first place. Now that we can mark individual parameters as erased, this method is fundamentally broken.

Related to #18472

@nicolasstucki nicolasstucki requested a review from Kordyjan August 30, 2023 09:22
@nicolasstucki nicolasstucki marked this pull request as ready for review August 30, 2023 12:09
@nicolasstucki nicolasstucki added this to the 3.4.0 milestone Oct 12, 2023
@dwijnand dwijnand modified the milestones: 3.4.0, 3.5.0 Dec 11, 2023
@nicolasstucki nicolasstucki modified the milestones: 3.5.0, 3.4.0 Dec 18, 2023
These methods should not have been stabiliezed in the first place.
Now that we can mark individual parameters as erased, this method is
fundamentally broken.
@nicolasstucki nicolasstucki assigned bishabosha and unassigned Kordyjan Dec 18, 2023
@nicolasstucki nicolasstucki requested review from bishabosha and removed request for Kordyjan December 18, 2023 13:30
* - Nth element is `FunctionN`
*/
@deprecated("Use overload of `FunctionClass` with 1 or 2 arguments","3.4")
@deprecated("Use overload of `FunctionClass` with 1 or 2 arguments", "3.4")
Copy link
Member

@bishabosha bishabosha Dec 19, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unrelated to this PR but this message seems ambiguous if we were to add another overload with 1 or 2 arguments, we might not catch it at the time those hypothetical methods would be added

@bishabosha bishabosha merged commit 8d9da73 into scala:main Dec 19, 2023
@bishabosha bishabosha deleted the deprecate-isErased branch December 19, 2023 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants