weaselab/conflict-set
2
0
Fork 0
Code Issues 4 Packages Releases 13 Activity

getBytes is currently const but not thread-safe #26

New Issue
Closed
opened 2024-05-03 01:12:43 +00:00 by andrew · 1 comment
andrew commented 2024-05-03 01:12:43 +00:00
Owner
Copy Link
No description provided.
andrew added the bug label 2024-05-03 01:12:49 +00:00
andrew commented 2024-05-03 01:16:01 +00:00
Author
Owner
Copy Link

Actually maybe this is ok, since there's only a data race when called concurrently with a non-const method

Actually maybe this is ok, since there's only a data race when called concurrently with a `non-const` method
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 enhancement
New feature
 investigation
wontfix
This won't be fixed
No Label bug
Milestone
No items
No Milestone
Assignees
Clear assignees
andrew jenkins
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: weaselab/conflict-set#26
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?