[chore] updates go-mutexes to no longer rely on unsafe linkname #3027
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Again, this is to prepare us for the Go 1.23 release. No more unsafe linkname in the mutex map, in fact most of the use wasn't really needed given sync.Cond{} is a thin wrapper around a runtime gated type. The only unsafe usage now in it is: https://codeberg.org/gruf/go-mutexes/src/commit/1a593cc53db2a09ec1c52e18797eaa625ea4292d/map.go#L188
The actual diff can be seen here: https://codeberg.org/gruf/go-mutexes/compare/v1.5.0...v1.5.1
Checklist
go fmt ./...
andgolangci-lint run
.