Debouncing still needed on autocomplete keypress?

1

Some time ago it was advised to use a debounce function wrapped around calling autocomplete (was firing too quickly and causing race conditions, displaying the options before picking up the users key input).

However, it seems a few things have changed since then and I’ve tried removing the debounce with no obvious negative effects now.

Do you think we can drop using a debounce now? Has something changed internally which means it’s probably no longer needed?

Thanks,
Matt

2

Two race conditions in show-hint were recently fixed. I don’t remember the discussion about debouncing, but yes, unless your completion function is very expensive, it should be fine to run completion without debounce.

3

Thanks. Will start using it without if it’s not really needed now.

Should I have a very expensive completion, would a debounce timeout of 0ms always be sufficient?