Skip to content

Commit

Permalink
improve wording of event type assignability rules
Browse files Browse the repository at this point in the history
This paragraph used to have a few sentences that used terms from
the bean type assignability part of the specification, which is
inappropriate for this part of the specification.
  • Loading branch information
Ladicek authored and manovotn committed Apr 26, 2023
1 parent 83c40ad commit b3ff532
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions spec/src/main/asciidoc/core/events.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -219,9 +219,9 @@ If the runtime type of the event object contains an unresolvable type variable,

==== Assignability of type variables, raw and parameterized types

An event type is considered assignable to a type variable if the event type is assignable to the upper bound, if any.
An event type is considered assignable to an observed event type that is a type variable if the event type is assignable to the upper bound of the type variable, if any.

A raw event type is considered assignable to a parameterized observed event type if the raw types are identical and all type parameters of the required type are either unbounded type variables or `java.lang.Object`.
A raw event type is considered assignable to a parameterized observed event type if the raw types are identical and all type parameters of the observed event type are either unbounded type variables or `java.lang.Object`.

A parameterized event type is considered assignable to a raw observed event type if the raw types are identical.

Expand Down

0 comments on commit b3ff532

Please sign in to comment.