Exact

Exact Union RegExp

Arne Welzel adf56ef4d8 Skip somer error reporting when the record type has errors ... The added test cases around function/event invocations report the following flurry of errors when only the first one is relevant and actionable. There's little use in reporting a mismatch with "error". Squelch them. error in <...>/function-invoke-mismatch-error.zeek, line 8: identifier not defined: MyEnumTypo error in <...>/function-invoke-mismatch-error.zeek, line 12 and error: type mismatch (M::MY_ENUM_A and error) error in <...>/function-invoke-mismatch-error.zeek, line 12: argument type mismatch in function call (M::to_string(M::MY_ENUM_A)) error in <...>/function-invoke-mismatch-error.zeek, line 16 and error: type mismatch (M::MY_ENUM_B and error) error in <...>/function-invoke-mismatch-error.zeek, line 16: argument type mismatch in function call (M::to_string(M::MY_ENUM_B)) error in <...>/function-invoke-mismatch-error.zeek, line 20 and error: type mismatch (M::e and error) error in <...>/function-invoke-mismatch-error.zeek, line 20: argument type mismatch in function call (M::to_string(M::e)) Record coercion also reports noisy errors when coercing to a type that has errors for individual fields, type clashing with "error": $ zeek language/record-field-error.zeek error in ./language/record-coerce-error.zeek, line 8: identifier not defined: MyEnumTypo error in ./language/record-coerce-error.zeek, line 19 and ./language/record-coerce-error.zeek, line 5: type clash for field "e" ((coerce [$e=MY_ENUM_B, $s=test] to MyRecord) and MyEnum)		2023-01-27 20:49:22 +01:00
..
out	Skip somer error reporting when the record type has errors	2023-01-27 20:49:22 +01:00