Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore] updates go-mutexes to no longer rely on unsafe linkname #3027

Conversation

NyaaaWhatsUpDoc
Copy link
Member

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

  • I/we have read the GoToSocial contribution guidelines.
  • I/we have discussed the proposed changes already, either in an issue on the repository, or in the Matrix chat.
  • I/we have not leveraged AI to create the proposed changes.
  • I/we have performed a self-review of added code.
  • I/we have written code that is legible and maintainable by others.
  • I/we have commented the added code, particularly in hard-to-understand areas.
  • I/we have made any necessary changes to documentation.
  • I/we have added tests that cover new code.
  • I/we have run tests and they pass locally with the changes.
  • I/we have run go fmt ./... and golangci-lint run.

@NyaaaWhatsUpDoc NyaaaWhatsUpDoc merged commit 9143ac6 into superseriousbusiness:main Jun 21, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants