You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We introduced a fancy feature about Lombok support that allows more accurate code navigation and refactoring for the lombok generated methods in #2339
Recently I found that the change to the JDTUtils.toLocation() might have some impact on the perf when the class has a large number of fields. See the profiling screenshots below:
Most of the execution time is taken by the newly added getGetter() & getSetter(). It's acceptable when those methods are invoked for code actions since they are triggered manually. While considering that document symbol calculation is a frequent request when user is typing. We might need to improve it.
We introduced a fancy feature about Lombok support that allows more accurate code navigation and refactoring for the lombok generated methods in #2339
Recently I found that the change to the
JDTUtils.toLocation()
might have some impact on the perf when the class has a large number of fields. See the profiling screenshots below:Most of the execution time is taken by the newly added
getGetter()
&getSetter()
. It's acceptable when those methods are invoked for code actions since they are triggered manually. While considering that document symbol calculation is a frequent request when user is typing. We might need to improve it.Steps to reproduce
The text was updated successfully, but these errors were encountered: