Nested records generates toplevel matchers

[runeflobakk]

E.g. if you have

package my.package;
public class TopLevel {
    public record R(int i) {}
}

The generated matcher will be:

package my.package;
public class RMatcher implements Matcher<TopLevel.R> { ... }

This means that if you have two records with the same (simple) name, defined in each of their top level class in the same package (which is perfectly valid), the code generator will (try to) generate an RMatcher for each of them in the same package, and thus resulting in a clash.

Possible solutions

• include the name of the top level class in the generated matcher's class name. I.e. in the example above, instead generate TopLevelRMatcher.
• other means for manually configuring resolution