Skip to content

Backport "Make isExactlyNothing and isExactlyAny work for And/OrTypes" to 3.7.4 #24054

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 23, 2025
Merged

Backport "Make isExactlyNothing and isExactlyAny work for And/OrTypes" to 3.7.4 #24054

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions compiler/src/dotty/tools/dotc/core/Types.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -244,13 +244,21 @@ object Types extends TypeUtils {
def isExactlyNothing(using Context): Boolean = this match {
case tp: TypeRef =>
tp.name == tpnme.Nothing && (tp.symbol eq defn.NothingClass)
case AndType(tp1, tp2) =>
tp1.isExactlyNothing || tp2.isExactlyNothing
case OrType(tp1, tp2) =>
tp1.isExactlyNothing && tp2.isExactlyNothing
case _ => false
}

/** Is this type exactly Any (no vars, aliases, refinements etc allowed)? */
def isExactlyAny(using Context): Boolean = this match {
case tp: TypeRef =>
tp.name == tpnme.Any && (tp.symbol eq defn.AnyClass)
case AndType(tp1, tp2) =>
tp1.isExactlyAny && tp2.isExactlyAny
case OrType(tp1, tp2) =>
tp1.isExactlyAny || tp2.isExactlyAny
case _ => false
}

Expand Down
Loading