964ac8b0e8
only two users of this function exist. only one used it in a way that even bears resemblance to asynchronicity, and even that one didn't do it right. fully async and parallel computation would have only worked if any getEdgesAsync never calls the continuation it receives itself, only from more derived callbacks running on other threads. calling it directly would cause the decoupling promise to be awaited immediately *on the original thread*, completely negating all nice async effects. Change-Id: I0aa640950cf327533a32dee410105efdabb448df |
||
---|---|---|
.. | ||
libexpr | ||
libexpr-support | ||
libstore | ||
libstore-support | ||
libutil | ||
libutil-support | ||
meson.build |