Files
scylladb/tests
Botond Dénes c899191ad5 reader_concurrency_semaphore: use the correct types in the constructor
Previously there was a type mismatch for `count` and `memory`, between
the actual type used to store them in the class (signed) and the type
of the parameters in the constructor (unsigned).
Although negative numbers are completely valid for these members,
initializing them to negative numbers don't make sense, this is why they
used unsigned types in the constructor. This restriction can backfire
however when someone intends to give these parameters the maximum
possible value, which, when interpreted as a signed value will be `-1`.
What's worse the caller might not even be aware of this unsigned->signed
conversion and be very suprised when they find out.
So to prevent surprises, expose the real type of these members, trusting
the clients of knowing what they are doing.

Also add a `no_limits` constructor, so clients don't have to make sure
they don't overflow internal types.

(cherry picked from commit e1d8237e6b)
2018-12-18 14:34:33 +02:00
..
2018-06-25 09:21:47 +01:00
2018-04-29 11:03:21 +03:00
2018-02-14 14:15:59 -05:00
2018-06-15 09:56:45 +01:00
2018-07-25 13:16:06 +02:00
2018-07-18 12:28:06 +01:00
2018-05-22 16:52:58 +02:00