3 Commits

Include renames

Author	SHA1	Message	Date
eldritch horrors	964ac8b0e8	libutil: de-callback-ify computeClosure ... 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	2024-05-07 14:35:20 +00:00
John Ericson	f4ab297b31	Ensure all headers have #pragma once and are in API docs ... `///@file` makes them show up in the internal API dos. A tiny few were missing `#pragma once`.	2023-03-31 23:19:44 -04:00
regnat	184558834a	Extract a generic computeClosure function ... Move the `closure` logic of `computeFSClosure` to its own (templated) function. This doesn’t bring much by itself (except for the ability to properly test the “closure” functionality independently from the rest), but it allows reusing it (in particular for the realisations which will require a very similar closure computation)	2021-05-19 11:44:58 +02:00