4 ms·
> "not really async, just timed" Let's bikeshed some more. > "And that's where this implementation fails: it makes it possible for a misbehaving 'async' call
by leokun 13y ago
> "not really async, just timed"
Let's bikeshed some more.
> "And that's where this implementation fails: it makes it possible for a misbehaving 'async' call (not really async, just timed) to hijack the editor and make it unusable."
Actually the patch now addresses all of these concerns, you can cancel the setTimeout scripts.
> "but considering that writing asynchronous/multi-threaded code is way harder than your usual linear Vim plugin"
Vim is not thread safe, you can't write a multi-threaded plugin with vim. It will break.
- jasonlotito 13y ago> Let's bikeshed some more. Bikeshedding is about things that really don't matter. However, something being timed or async do matter. Describing something as async when it's not destroys the meaning of async and confuses what it really does. At the very least, describe it as "blocking async" so it's clear what it is. Basically, call it what you will, but if you describe it as async, I expect it will be non-blocking because that's what async is by default.
- leokun 13y agoIt's the exact same thing that happens in the browser. If you write a setTimeout and never let go, like a never ending while loop it will block your browser forever.