tree ed9474b677124ea8e048c0832494f3114c267fe5
parent 9f804a82a86288e9f19079197a480968ce5a54ca
author Christoffer Quist Adamsen <christofferqa@google.com> 1530780566 +0200
committer Christoffer Quist Adamsen <christofferqa@google.com> 1530780566 +0200

Improve performance of collision detection

The collision detection works by collecting all the targeted method signatures in the program, and then checking before each merge operation, if that merge operation could lead to a collision, by considering all the signatures that have been collected.

The current implementation only considers the targeted method signatures that references at least one program type. This CL adds two optimizations: it considers only those method signatures that references at least one merge or mergee candidate, and it also only considers methods that are potentially overloaded.

On GMS Core, this reduces the running time of the collision detector from approx. 25 seconds to 2 seconds.

Change-Id: I8395fa01b61b98c937fe53d2a09b3b13f81b14f2