In the spec there is no overload that could match null < x, so implementations should be allowed to fail type checking for this.
Cel-go doesn't, because it considers well-known types nullable, so e.g the overload timestamp < timestamp matches this at type-checking (but not at run-time).
In the spec there is no overload that could match null < x, so implementations should be allowed to fail type checking for this.
Cel-go doesn't, because it considers well-known types nullable, so e.g the overload timestamp < timestamp matches this at type-checking (but not at run-time).