For signals and possibly functions that are throttled or debounced, it would be very useful to allow some form of cancellation.
As an example, consider a throttled search query; if the user is typing in an input element and then hits enter, what should happen? I think the natural expectation is that the query executes immediately. As they exist now, these deferred signals and functions can't easily provide this functionality.
I'm not sure cancel fully captures my thinking, here. There are really two distinct ideas:
- Cancel any throttled or debounced action without setting any signals or calling functions.
- Call the function or update the signal immediately and cancel any awaiting changes.
I'm not sure if one or both of these is important enough to be included by default, but at the very least it would be awesome to have a set of throttled/debounced functions/signals that can be cancelled!
For signals and possibly functions that are throttled or debounced, it would be very useful to allow some form of cancellation.
As an example, consider a throttled search query; if the user is typing in an input element and then hits enter, what should happen? I think the natural expectation is that the query executes immediately. As they exist now, these deferred signals and functions can't easily provide this functionality.
I'm not sure cancel fully captures my thinking, here. There are really two distinct ideas:
I'm not sure if one or both of these is important enough to be included by default, but at the very least it would be awesome to have a set of throttled/debounced functions/signals that can be cancelled!