Remove unsafe from BeetsLibraryCommandExecutor #22

Closed
opened 2023-04-10 21:39:43 +02:00 by wojtek · 0 comments
Owner

For the same reason why File::open does not have unsafe. The behaviour is not unsafe as it does not lead to undefined behaviour within the program itself. The bug from #18 was just a typical testing bug as described in https://doc.rust-lang.org/book/ch11-02-running-tests.html#running-tests-in-parallel-or-consecutively. Correct Send and Sync behaviour is ensured by correctly using &mut self.

For the same reason why File::open does not have unsafe. The behaviour is not unsafe as it does not lead to undefined behaviour within the program itself. The bug from #18 was just a typical testing bug as described in https://doc.rust-lang.org/book/ch11-02-running-tests.html#running-tests-in-parallel-or-consecutively. Correct `Send` and `Sync` behaviour is ensured by correctly using `&mut self`.
wojtek added this to the mvp (v0.1.0) milestone 2023-04-10 21:39:43 +02:00
wojtek added the
bug
label 2023-04-10 21:39:43 +02:00
wojtek added reference 22---remove-unsafe-from-beetslibrarycommandexecutor 2023-04-10 21:51:54 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: wojtek/musichoard#22
No description provided.