Multi-threading and/or multi-processing with NoGraphs?

[HeWeMel]

So far, only the application itself can use multi-threading and multi-processing, e.g., when computing the next vertices or edges of a vertex. And the application has to deal with parallelism on its own.

Does it make sense that NoGraphs supports multi-threading and/or multi-processing in some way? And how?

[HeWeMel]

Idea: There could be a variant of BFS that supports bulk computation of next vertices/edges for a whole set of vertices. Like this, the application could better use multi-threading and multi-processing on its side.

(Like this, NoGraphs would support parallelism indirectly, by making live easier for the application)

[HeWeMel]

Idea: There could be a variant of BFS that asks for next vertices/edges and uses multi-threading and/or multi-processing to leverage parallelism at least for the computations done by the application. Like this, the application does not need to implement parallelism on its own.