Skip to content

perf: Avoid frequent save-excursion calls in the citre-completion-at-point function.#192

Closed
milanglacier wants to merge 1 commit intouniversal-ctags:masterfrom
milanglacier:master
Closed

perf: Avoid frequent save-excursion calls in the citre-completion-at-point function.#192
milanglacier wants to merge 1 commit intouniversal-ctags:masterfrom
milanglacier:master

Conversation

@milanglacier
Copy link
Copy Markdown
Contributor

@milanglacier milanglacier commented Sep 24, 2025

The function call chain citre-completion-at-point -> citre-tags-get-completion-at-point -> citre-tags-get-symbol-default eventually calls citre-bounds-of-sym-or-op-at-point.

Calling save-excursion in citre-bounds-of-sym-or-op-at-point repeatedly during completion is expensive.

Furthermore, checking if the point is at an operator is unnecessary, as completion candidates typically do not include operators.

…nt` function.

Calling `save-excursion` repeatedly during completion is
computationally expensive. Furthermore, checking if the point is at an
operator is unnecessary, as completion candidates typically do not
include operators.
@milanglacier milanglacier changed the title perf: Avoid frequent save-excursion calls in the completion-at-point function. perf: Avoid frequent save-excursion calls in the citre-completion-at-point function. Sep 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant