Make sure we don't copy or move Storage

google / marl

A hybrid thread / fiber task scheduler written in C++ 11

Apache License 2.0

1.89k stars 193 forks source link

Make sure we don't copy or move Storage #255

Closed fmayer closed 1 year ago

fmayer commented 1 year ago

It is inherently not safe to copy because it owns the Item pointers. It does not seem to be written in a way that takes care that it is move-safe either.