Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Properly identify empty bounds in error message #19310

Merged
merged 1 commit into from
Dec 21, 2023
Merged

Properly identify empty bounds in error message #19310

merged 1 commit into from
Dec 21, 2023

Conversation

nicolasstucki
Copy link
Contributor

This caused a trailing space which can easily misbehave in checkfiles.

@nicolasstucki
Properly identify empty bounds in error message
63bf7f3 
This caused a trailing space which can easily misbehave in checkfiles.
@nicolasstucki nicolasstucki marked this pull request as ready for review December 21, 2023 09:28
@nicolasstucki nicolasstucki merged commit 0336e68 into scala:main Dec 21, 2023
19 checks passed
@nicolasstucki nicolasstucki deleted the properly-identify-empty-bounds-in-error-message branch December 21, 2023 10:20
@Kordyjan Kordyjan added this to the 3.4.1 milestone Feb 14, 2024
@WojciechMazur WojciechMazur mentioned this pull request Jun 25, 2024
Merged
WojciechMazur added a commit that referenced this pull request Jun 26, 2024
@WojciechMazur
Backport "Properly identify empty bounds in error message" to LTS (#2…
ab88fbf 
…0806)

Backports #19310 to the LTS branch.

PR submitted by the release tooling.
[skip ci]
# for free to join this conversation on GitHub. Already have an account? # to comment
Reviewers

@sjrd sjrd sjrd approved these changes

Assignees

@sjrd sjrd

Labels
None yet
Projects
None yet
Milestone
3.4.1
Development

Successfully merging this pull request may close these issues.
3 participants
@nicolasstucki @sjrd @Kordyjan