It has come to my attention that certain methods from the Java language classes may incorporate generic types, such as requireNonNull(T). Unfortunately, this can lead to confusion for Specimin (more specifically, JavaParser), causing it to mistakenly classify these methods as unresolved and generate unnecessary synthetic classes. To resolve this issue, we can implement a straightforward solution: ensuring that Specimin refrains from generating synthetic files for classes originating from the Java language.
Please note that we already have a check in place (line 2272) to address a similar problem with classes from the original codebase.
Professor,
It has come to my attention that certain methods from the Java language classes may incorporate generic types, such as
requireNonNull(T). Unfortunately, this can lead to confusion for Specimin (more specifically, JavaParser), causing it to mistakenly classify these methods as unresolved and generate unnecessary synthetic classes. To resolve this issue, we can implement a straightforward solution: ensuring that Specimin refrains from generating synthetic files for classes originating from the Java language.Please note that we already have a check in place (line 2272) to address a similar problem with classes from the original codebase.
Please take a look. Thank you.