Ukko, 5 months ago future cannot be sent between threads safely fuck you I am rewriting all of this into Python
future cannot be sent between threads safely fuck you I am rewriting all of this into Python
subtype, 5 months ago @Ukko can’t have thread problems if everything is behind a global interpreter lock :brain10:
@Ukko can’t have thread problems if everything is behind a global interpreter lock :brain10:
Ukko, 5 months ago @subtype Python is dropping the GIL pretty soon IIRC
@subtype Python is dropping the GIL pretty soon IIRC
subtype, 5 months ago @Ukko if you want to ignore Sync and Send errors in Rust (I assume that was OP about?) you can just unsafe impl Send for Foo {}; 🙃
@Ukko if you want to ignore Sync and Send errors in Rust (I assume that was OP about?) you can just
Sync
Send
unsafe impl Send for Foo {};
🙃
Ukko, 5 months ago @subtype nah i am not touching others structs
@subtype nah i am not touching others structs
Ukko, 5 months ago @subtype I am having a skill issue so I will just Python
@subtype I am having a skill issue so I will just Python
subtype, 5 months ago @Ukko Oh ok, looks like someone fucked up if the future isn't sync. Or maybe it became so because you put a non-sync type into it?
@Ukko Oh ok, looks like someone fucked up if the future isn't sync. Or maybe it became so because you put a non-sync type into it?
Ukko, 5 months ago @subtype Yes
@subtype Yes
Add comment