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
/// * [Integer](https:/redis.io/docs/reference/protocol-spec#integers): the position of the first bit set to 1 or 0 according to the request
304
304
/// * [Integer](https:/redis.io/docs/reference/protocol-spec#integers): `-1`. In case the `bit` argument is 1 and the string is empty or composed of just zero bytes
305
-
///
305
+
///
306
306
/// If we look for set bits (the bit argument is 1) and the string is empty or composed of just zero bytes, -1 is returned.
307
-
///
307
+
///
308
308
/// If we look for clear bits (the bit argument is 0) and the string only contains bits set to 1, the function returns the first bit not part of the string on the right. So if the string is three bytes set to the value `0xff` the command `BITPOS key 0` will return 24, since up to bit 23 all the bits are 1.
309
-
///
309
+
///
310
310
/// The function considers the right of the string as padded with zeros if you look for clear bits and specify no range or the _start_ argument **only**.
311
-
///
311
+
///
312
312
/// However, this behavior changes if you are looking for clear bits and specify a range with both _start_ and _end_.
313
313
/// If a clear bit isn't found in the specified range, the function returns -1 as the user specified a clear range and there are no 0 bits in that range.
314
314
@inlinable
@@ -442,13 +442,13 @@ extension RedisConnection {
442
442
/// - Returns: One of the following:
443
443
/// * [Integer](https:/redis.io/docs/reference/protocol-spec#integers): the position of the first bit set to 1 or 0 according to the request
444
444
/// * [Integer](https:/redis.io/docs/reference/protocol-spec#integers): `-1`. In case the `bit` argument is 1 and the string is empty or composed of just zero bytes
445
-
///
445
+
///
446
446
/// If we look for set bits (the bit argument is 1) and the string is empty or composed of just zero bytes, -1 is returned.
447
-
///
447
+
///
448
448
/// If we look for clear bits (the bit argument is 0) and the string only contains bits set to 1, the function returns the first bit not part of the string on the right. So if the string is three bytes set to the value `0xff` the command `BITPOS key 0` will return 24, since up to bit 23 all the bits are 1.
449
-
///
449
+
///
450
450
/// The function considers the right of the string as padded with zeros if you look for clear bits and specify no range or the _start_ argument **only**.
451
-
///
451
+
///
452
452
/// However, this behavior changes if you are looking for clear bits and specify a range with both _start_ and _end_.
453
453
/// If a clear bit isn't found in the specified range, the function returns -1 as the user specified a clear range and there are no 0 bits in that range.
/// * [Integer](https:/redis.io/docs/reference/protocol-spec#integers): `0` if the timeout was not set. For example, if the key doesn't exist, or the operation was skipped due to the provided arguments.
/// Returns the expiration time of a key as a Unix timestamp.
@@ -986,7 +986,7 @@ extension RedisConnection {
986
986
/// * [Integer](https:/redis.io/docs/reference/protocol-spec#integers): `0` if the timeout was not set. For example, if the key doesn't exist, or the operation was skipped due to the provided arguments.
0 commit comments