Re: Updating *Completions* as you type

[Eli Zaretskii]

> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: Spencer Baugh <sbaugh@janestreet.com>,  emacs-devel@gnu.org
> Date: Sat, 14 Oct 2023 22:26:52 +0300
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> > IIUC what you mean by "asynchronous completion", it is a terrible
> >> > idea.  How can anyone type text without getting immediate feedback for
> >> > what he/she typed?  When I sometimes see this (due to network delays
> >> > or system load or whatever), it is a terrible UX.
> >> 
> >> By asynchronous completion, I just mean being able to type, and trigger
> >> completion, and have completions appear incrementally as they are
> >> computed, without interfering with you continuing to type.  I don't
> >> think that stops immediate feedback for typing.
> >
> > If it's asynchronous, then how can we make sure the feedback is
> > immediate?
> 
> The feedback updates while typing but doesn't show until the delay set
> by the user has passed to show the suggestions again.

This sentence seems to contradict itself: what is the meaning of
"feedback updates" if the feedback "doesn't show"?

> If the feedback hasn't updated by the time the user stops typing then
> the old state is shown similar to how  the feedback is when the
> completion is synchronous.

I don't understand this, either.  Please elaborate, or maybe show an
example.