Stefan Monnier <[email protected]> writes: >> Obviously, we need some design how to handle asynchronous file >> operations. Any proposals? > > I think it requires fairly major changes: you can't just make > insert-file-contents asynchronous because its behavior is defined (and > assumed by callers) to be synchronous. > > I.e. you need a new way to "insert asynchronously". It can be via a new > function `insert-file-asynchronously' or via a new argument (or special > arg value) of insert-file-contents, so that insert-file-contents knows > that the caller expects an async behavior. > > And then all the callers that want to support async operations need to > be rewritten (and some of their callers as well).
All of this agreed. That's why I've started with my question. > Maybe working on the concurrency branch would be easier and more useful. Yes, this might help. But you still need a kind of infrastructure as you have pointed out above. Would those new APIs differ, when the implementation is based on threads, instead of of what I'm doing now? > Stefan Best regards, Michael. _______________________________________________ Tramp-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/tramp-devel
