Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

tokio-rs / tokio Public

Notifications You must be signed in to change notification settings
Fork 2.5k
Star 27.4k

Code
Issues 289
Pull requests 36
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

sync: ensure Mutex, RwLock, and Semaphore futures are Send + Sync#2375

Merged

carllerche merged 5 commits intomastertokio-rs/tokio:masterfrom eliza/semaphore-synctokio-rs/tokio:eliza/semaphore-syncCopy head branch name to clipboard

Apr 3, 2020

+39-3

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Apr 3, 2020

sync: Add bounds checks for Send + Sync futures
hawkw
committed
sync: ensure Mutex, RwLock, and Semaphore futures are Send + Sync
hawkw
committed
fix unused variable in checks
hawkw
committed
prepare to release 0.2.16
hawkw
committed
fix wrong version

hawkw
and
carllerche
authored

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.