From 8802a5d740d6cff29e473e7e0507b6a6d40a55e4 Mon Sep 17 00:00:00 2001 From: _ov4 Date: Thu, 22 Oct 2026 15:04:13 +0000 Subject: fix(codegen): name both operand types in invalid operator diagnostics Updates the operator-global-errors and string-type-mismatch expectations to the new "Operator X cannot be applied to A and B" wording. Co-Authored-By: Claude Sonnet 5.5 --- lib/CodeGen/TypeCheckGen.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lib') diff --git a/lib/CodeGen/TypeCheckGen.cc b/lib/CodeGen/TypeCheckGen.cc index 575fc04..ef079b7 100644 --- a/lib/CodeGen/TypeCheckGen.cc +++ b/lib/CodeGen/TypeCheckGen.cc @@ -111,8 +111,8 @@ Value *CodeGen::emitUserKindBinaryOp(int Op, Value *L, const TypeInfo *LT, const char *RName = RT ? RT->Name.c_str() : "?"; if ((LT && LT->isRecord()) || (RT && RT->isRecord())) { - reportError("Operator %s cannot be applied to a record value (type %s)", - operatorSpelling(Op).c_str(), (LT && LT->isRecord()) ? LName : RName); + reportError("Operator %s cannot be applied to %s and %s", + operatorSpelling(Op).c_str(), LName, RName); return nullptr; } -- cgit v1.3.1-4-g156e