Resources are marked as !Send and !Sync?

[simast]

Struggling a bit with the Resources container from legion. I want to store terrain heightmap as part of resources, so it is a significant chunk of data. Was just thinking I could create the following struct:

struct Game {
    world: World,
    resources: Resources,
}

And then create a new instance of Game in a separate thread and send it back to the main thread (with thread::spawn and mpsc channels). Basically so I do not block the main UI thread while the game is starting up or being loaded from disk.

But digging in the code I see Resources is actually explicitly marked as not !Send in legion code:

_not_send_sync: PhantomData<*const u8>,

So that does not seem to be an option. Also Resources::insert() consumes the value, so I am really puzzled how can I implement loading of resources in a separate thread here, without resorting to copying and cloning data around.

Any hints or best practices or good examples for Resources usage?

[simast]

Well, after a good nights sleep I figured I can solve this by manually marking mentioned Game struct with a Send:

unsafe impl Send for Game {}

Will close this issue.

[zedrian]

Looks like you hacked Legion, but if that works normally, then okay :)