Improve refactoring performance

nittka commented 8 years ago

As indicated in #107, the refactoring participants affect performance. One major reason is that going through the includes in order to find out potential problems is not optimal. Each file is parsed (over and over in case of folder deletes) again... But this is what the index is for. What I propose to do is

use injection for creating the refactoring participants
inject the index
add custom information to the index about direct includes for each resource
use that information for calculating dependencies relevant for the refactoring
actually use the cancel indicator to abort an operation

Note that the index information about includes can only be partial (includes with variables, whose value may come from wherever). (Depending on when @thSoft plans a new release, I can work on this issue starting 07/17...)

nittka commented 8 years ago

I was able to start earlier on this issue, so a first potential solution is available.

nittka commented 8 years ago

The refactoring has been reimplemented, including performance improvements. All relevant changes are included in pull request #119,

thSoft / elysium

Improve refactoring performance #118