You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assume we could still do things in parallel if we want.
We could create a DisjointViews (or so) struct that holds non-overlapping ArrayBytesFixedDisjointViews and has a safe fn add(&mut self, ...) -> bool that returns if a region was safely added (would not overlap with the already contained regions) or not. Then at runtime,
create a Vec<DisjointViews> by first trying to add each view to the first DisjointViews object, then the second, … until each view has been added.
go over the vec and handle each DisjointViews object in parallel.
There could be pathological cases where that doesn’t work well, but in practice, those shouldn’t happen
The text was updated successfully, but these errors were encountered:
See #87 (comment)
I assume we could still do things in parallel if we want.
We could create a
DisjointViews
(or so) struct that holds non-overlappingArrayBytesFixedDisjointView
s and has a safefn add(&mut self, ...) -> bool
that returns if a region was safely added (would not overlap with the already contained regions) or not. Then at runtime,Vec<DisjointViews>
by first trying to add each view to the firstDisjointViews
object, then the second, … until each view has been added.DisjointViews
object in parallel.There could be pathological cases where that doesn’t work well, but in practice, those shouldn’t happen
The text was updated successfully, but these errors were encountered: