dotOperators, callOperator produce bad/misleading undeclared field error msgs

[timotheecour]

when a dotOperators is defined (with {.experimental: "dotOperators".}), it affects unrelated undeclared field error messages.

Example 1

{.experimental: "dotOperators".}
type Foo = object
template `.`(a: Foo, b: untyped): untyped = 123
type Bar = object
  x1: int
var b: Bar
echo b.x

Current Output

Error: type mismatch: got <Bar>
but expected one of:
template `.`(a: Foo; b: untyped): untyped
  first type mismatch at position: 1
  required type for a: Foo
  but expression 'b' is of type: Bar

expression: x(b)
  echo b.x

Expected Output

should contain the following errmsg which is what we get without template .(a: Foo, b: untyped): untyped = 123:

Error: undeclared field: 'x' for type t0892.Bar [declared in t0892.nim(11, 6)]
  echo b.x

in addition to the above errmsg Error: type mismatch: got <Bar>...

Example 2

callOperator has the same problems

Additional Information

• recent devel ba4fbb6
• this would be mitigated but not fixed by Force experimental switch to be able to use call/dot operators #16924

[timotheecour]

@hlaaftana do you have any interest in working on this since you've looked at related code with #16924? this issue makes it awkward to use things like wrapnils or jsffi etc, since (even after your PR, albeit less so) you get bad errors

[treeform]

I love dotOperators, except for this bug they are perfect. Can't wait for it to be fixed.