[DiscordArchive] how many threads can update _cacheState ? 1 or more ?
[DiscordArchive] how many threads can update _cacheState ? 1 or more ?
Original source
but this is stupid
rektbyfaith
07-17-2024, 08:18 PM #41Archived author: Tea • Posted: 2024-07-17T20:18:16.867000+00:00
Original source
but this is stupid
Original source
std::future destructor will block if it was obtained by using std::async...
rektbyfaith
07-17-2024, 08:18 PM #42Archived author: Tea • Posted: 2024-07-17T20:18:39.129000+00:00
Original source
std::future destructor will block if it was obtained by using std::async...
Original source
https://en.cppreference.com/w/cpp/thread.../%7Efuture
[Embed: cpp/thread/future/~future]
https://en.cppreference.com/w/cpp/thread.../%7Efuture
rektbyfaith
07-17-2024, 08:18 PM #43Archived author: Tea • Posted: 2024-07-17T20:18:42.645000+00:00
Original source
https://en.cppreference.com/w/cpp/thread.../%7Efuture
[Embed: cpp/thread/future/~future]
https://en.cppreference.com/w/cpp/thread.../%7Efuture
Original source
Yeah
rektbyfaith
07-17-2024, 08:18 PM #44Archived author: Foe • Posted: 2024-07-17T20:18:47.303000+00:00
Original source
Yeah
Original source
So the only "*good*" solution I could find was to either do it like I did with detach, write a worker and wait in the deinit for a stop signal, or do some lambda black magic that just looked cursed
rektbyfaith
07-17-2024, 08:20 PM #45Archived author: Foe • Posted: 2024-07-17T20:20:26.951000+00:00
Original source
So the only "*good*" solution I could find was to either do it like I did with detach, write a worker and wait in the deinit for a stop signal, or do some lambda black magic that just looked cursed
Original source
isn't it enough to store the std::future in the class as a member ?
rektbyfaith
07-17-2024, 08:22 PM #46Archived author: jackpoz • Posted: 2024-07-17T20:22:09.217000+00:00
Original source
isn't it enough to store the std::future in the class as a member ?
Original source
if you were trying to be fancy, you would use std:
hared_future<void> and give to all the states that are going to be reloaded, replacing the bool reload member
rektbyfaith
07-17-2024, 08:25 PM #47Archived author: Tea • Posted: 2024-07-17T20:25:27.033000+00:00
Original source
if you were trying to be fancy, you would use std:hared_future<void> and give to all the states that are going to be reloaded, replacing the bool reload member
Original source
feels overengineered
rektbyfaith
07-17-2024, 08:25 PM #48Archived author: Tea • Posted: 2024-07-17T20:25:35.228000+00:00
Original source
feels overengineered
Original source
Yeah..
rektbyfaith
07-17-2024, 08:25 PM #49Archived author: Foe • Posted: 2024-07-17T20:25:54.818000+00:00
Original source
Yeah..
Original source
I'll probably try to play around with freezing the reload thread over the weekend and see if it crashes on shutdown, pretty sure it will
rektbyfaith
07-17-2024, 08:33 PM #50Archived author: Foe • Posted: 2024-07-17T20:33:07.405000+00:00
Original source
I'll probably try to play around with freezing the reload thread over the weekend and see if it crashes on shutdown, pretty sure it will
1 Guest(s)
1 Guest(s)