Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUnnecessary use of IpcSender/IpcReceiver in FontCacheThread::exit #9373
Comments
|
Can I try my hand at this? Disclaimer: I might need to ping you if I don't get something at first; I'm new to Rust/Servo. :) |
|
Sure thing! Come to #servo on |
|
Not quite clear this is possible:
|
This allows unifying the way we prevent the serialisation of things that can't be sent over IPC for their in-process nature. This is a proposed solution to things like: servo#9373 Where something like the following can be used: ```rust Exit(Unserializable<Sender<()>>), ```
This allows unifying the way we prevent the serialisation of things that can't be sent over IPC for their in-process nature. This is a proposed solution to things like: servo#9373 Where something like the following can be used: ```rust Exit(Unserializable<Sender<()>>), ```
|
I apologize for proposing an impossible change (at least without @ecoal95's experiment). The proper way to solve this would be to split the Command enum into two, and use |
While investigating servo/ipc-channel#29 I realized that the existing code is inefficient. We can use a regular std::sync::mpsc channel instead of the equivalent from ipc-channel, since both the Constellation and FontCacheThread code run in the same process.
Code:
components/gfx/font_cache_thread.rs, in theexitfunction