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
When searching for symbol references, the search box should how snippets of code which reference the symbol for ease of use. (https://grep.app has a fantastic implementation of this)
The text was updated successfully, but these errors were encountered:
how do you propose we handle the biggest issue with this -- we don't have access to the source
we would have to decompile the full jar in order to implement this feature, and I'm not sure what a good way to go about that is
how do you propose we handle the biggest issue with this -- we don't have access to the source
we would have to decompile the full jar in order to implement this feature, and I'm not sure what a good way to go about that is
Literally just decompile it like you said, on a another thread. The source code isn't going to change much anyways, except for renaming some symbols.
There isn't much optimisations you can do, but remember this is a one-time operation per project. It may take a while initially, but at least we aren't wasting computational power on re-indexing and decompiling the JAR every time you load the project.
When searching for symbol references, the search box should how snippets of code which reference the symbol for ease of use. (https://grep.app has a fantastic implementation of this)
The text was updated successfully, but these errors were encountered: