Files
turso/core
Pere Diaz Bou cb4efdbc19 Merge 'LimboRwLock write and read lock fixes' from Pere Diaz Bou
* `write` was returning `true` even though it shouldn't because it
should return `false` in case it was already acquired.
* `read` theoritically can increase `nread` after another thread calls
`unlock` between first lock load and increase of `nread`. So it looks
something like this:
                  1. THREAD  1: read()
                  2. THREAD 2: get lock = `SHARED_LOCK`
                  3. THREAD 1: unlock -> lock is now `NO_LOCK`
                  4. THREAD 2: increase nread, return true.
    This is obviously wrong because `nreads` will be ` > 0 ` but `lock`
is `NO_LOCK`

Closes #1676
2025-06-09 16:15:46 +02:00
..
2025-05-23 12:37:03 -03:00
2025-05-15 09:59:46 +03:00
2025-05-15 09:59:46 +03:00
2025-05-30 13:07:31 +02:00
2025-04-23 08:34:58 -03:00
2025-05-15 09:59:46 +03:00
2025-01-28 14:55:38 -05:00
2025-04-24 11:05:21 +03:00
2025-01-28 14:55:38 -05:00
2025-05-15 09:59:46 +03:00
wip
2025-03-29 22:02:49 +01:00
2024-12-24 18:04:30 +01:00
2025-06-07 10:11:47 +03:00
2025-06-01 07:45:57 +02:00