Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
2 edited tags
| link
1
source | link

Speed issue with omnisharp go-to-definition

Getting a rather sizable speed issue with using go-to-definition from omnisharp. Ran the profiler, and received nearly 50% of the cpu time dedicated between:

isearch-printing-char

and

omnisharp-go-to-definition

The former was 9% larger than the latter. Anyone else experience this issue?

Modes I'm currently running on the buffers that are starting the function call:

C#, company, flychec, yas, projectile, ws