Skip to content

Commit

Permalink
Properly identify empty bounds in error message (#19310)
Browse files Browse the repository at this point in the history
This caused a trailing space which can easily misbehave in checkfiles.
  • Loading branch information
nicolasstucki authored Dec 21, 2023
2 parents d3fafd6 + 63bf7f3 commit 0336e68
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion compiler/src/dotty/tools/dotc/reporting/Message.scala
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,7 @@ object Message:
}

def addendum(cat: String, info: Type): String = info match {
case bounds @ TypeBounds(lo, hi) if bounds ne TypeBounds.empty =>
case bounds @ TypeBounds(lo, hi) if !(bounds =:= TypeBounds.empty) =>
if (lo eq hi) i" which is an alias of $lo"
else i" with $cat ${boundsStr(bounds)}"
case _ =>
Expand Down
2 changes: 1 addition & 1 deletion tests/neg/i13780-1.check
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
| Required: h
|
| where: VS is a type in method foo with bounds <: Tuple
| h is a type in method foo with bounds
| h is a type in method foo
| t is a type in method foo with bounds <: Tuple
|
|
Expand Down

0 comments on commit 0336e68

Please sign in to comment.