jean pierre Lerbscher

This is not trivial, because to resolve the println(..) method Javaparser has to resolve the type of the parameter, which is undefined at this stage. I don't see any precision...

Please don't mix issues.

Javaparser already has a cache to prevent certain costly operations from being re-executed. You can also add caching to your own code if you wish, but if you propose a...

It's a complicated case and I'm surprised that you're the first person to spot this issue. Unfortunately I'm not going to be able to solve it immediately. No matter how...

This is a bug that has already been identified but for which we do not yet have a solution. It appears when JP tries to resolve a symbol in a...

Related to https://github.com/javaparser/javaparser/issues/3674

Thank you for your hard work, but i can't validate this PR because it mixes several concepts and doesn't take into account all the JP components (for example, I can't...

> About the generated part... I reverse enginered it. Tests prove that the code is doing what it is expected to. Have you used the generators to generate code for...

Non-preview java 21 features have been implemented in version 3.26.0.

I need to take some time to look at this proposal.