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
Your implementation of RWLock based on two mutexes requires that a mutex acquired by one thread can be released by another, which is not the case with the pthread_mutex implementation. What is on purpose? In my project, I solved this by implementing RWLock directly with pthread_rwlock instead.
When reaching this issue, I have also noticed that you do not check the result of these calls in RecursiveMutex. It would be great to throw proper errors here like you are doing when initialising the mutex.
Let me know if you would be interested by a PR.
The text was updated successfully, but these errors were encountered:
Your implementation of
RWLock
based on two mutexes requires that a mutex acquired by one thread can be released by another, which is not the case with thepthread_mutex
implementation. What is on purpose? In my project, I solved this by implementingRWLock
directly withpthread_rwlock
instead.When reaching this issue, I have also noticed that you do not check the result of these calls in
RecursiveMutex
. It would be great to throw proper errors here like you are doing when initialising the mutex.Let me know if you would be interested by a PR.
The text was updated successfully, but these errors were encountered: