The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
emails
Posts with mentions or reviews of emails.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-03.
-
Bug in std:shared_mutex on Windows
Unfortunately, the opposite of that is everybody trying to file random things that aren't actionable. See the collection of mail sent to the curl maintainer…
https://github.com/bagder/emails/blob/main/2015/2015-06-08.m...
-
Emails I Received, the Collection
This one is funny: https://github.com/bagder/emails/blob/main/2016/2016-01-19.m...
The smooth changes of tone between strong arming and pleading with Daniel are just incredible.
- Funny Emails to Curl Developer
- Curl maintainers' collection of offensive emails
SRW-2
Posts with mentions or reviews of SRW-2.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-03.
-
Bug in std:shared_mutex on Windows
https://github.com/rbmm/SRW-2 - possible better repro code . where i guarantee repro this without hundreds loops. i be say that "question" in RtlReleaseSRWLockExclusive implementation. it first remove Lock bit from SRW (and after this any thread can enter to lock) and then call RtlpWakeSRWLock. but this 2 operations not atomic. if in the middle (after Lock Bit removed and before RtlpWakeSRWLock executed) another thread acquire shared access - it got exclusive. and RtlpWakeSRWLock also "fail" after this - not wake any waiters. but when shared/exlusive owner then release lock..RtlpWakeSRWLock will be called again and self job. i be of course use bit another implementation, link to which i paste in another comment here
What are some alternatives?
When comparing emails and SRW-2 you can also consider the following projects:
boto3 - AWS SDK for Python
cpp-docs - C++ Documentation
PushLock - Lock Tests
SRW_ALT