Bad interaction between autoclonetype and the compiler plugin

[jackkoenig]

I haven't been able to identify exactly what the issue is, but sometimes you can get a NullPointerException in autoclonetype when using the compiler plugin. The issue shows up in v3.4.1 and v3.4.2.

Showing issue: https://scastie.scala-lang.org/urTiFHCRRB6mWWUFjKJ6xw
v3.4.2 no plugin no issue: https://scastie.scala-lang.org/Q9cb7NnETDq8p6B2tkWVaA
v3.4.1 plugin has issue: https://scastie.scala-lang.org/awinn0u7QeCr9GyMQkLHNw
v3.4.0 plugin no issue: https://scastie.scala-lang.org/nwuijlIuQDChB3zSjEi8cQ

If you hit Download on Scastie, you can reproduce locally. Notably, Scastie adds partial unification and kind projector plugins which I think are part of the problem.

I believe the issue is also related to #1660 (released in v3.4.1) which made autoNameRecursively lazy.

I believe this issue will be fixed by my forthcoming compiler plugin autoclonetype

Type of issue: bug report

Impact: no functional change

Development Phase: request

Other information

If the current behavior is a bug, please provide the steps to reproduce the problem:

What is the current behavior?

What is the expected behavior?

Please tell us about your environment:

What is the use case for changing the behavior?