Closed blueyed closed 6 years ago
After deoplete moved to multiprocessing ("one source -- one process") model this spring, I don't see many reasons to write async
plugins (in deoplete terms) anymore. You can just block whatever you want and neither editor nor deoplete core will be blocked because of that.
Yep, closing.
I've thought about using asyncio with deoplete, but that would still allow sources to block, of course.
Thanks for the update!
deoplete has async support for sources by now, which could be used probably with the async work that has been done here lately.
Haven't investigated, but wanted to open this for ideas/discussion already.