--- Comment #7 from Sven Brauch <> ---
Most of the delay you see is a delay, not the parser being slow. The point is
that, right now, as soon as the parser starts you need to wait for it to finish
before you can generate a completion list. Thus the delay, and thus changing
the delay based on processor speed doesn't help -- it's meant to match your
typing speed, not the processor.

The parser is slow because parsing C++ correctly is complicated.

This issue has nothing to do with the size of whatever cache you're thinking

You are receiving this mail because:
You are watching all bug changes.

Reply via email to