Add bssl::Span<T>::subspan and use it. This roughly aligns with absl::Span<T>::subspan. Bug: 132 Change-Id: Iaf29418c1b10e2d357763dec90b6cb1371b86c3b Reviewed-on: https://boringssl-review.googlesource.com/20824 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Martin Kreichgauer <martinkr@google.com>
diff --git a/ssl/t1_lib.cc b/ssl/t1_lib.cc index 1fe360b..3b0a335 100644 --- a/ssl/t1_lib.cc +++ b/ssl/t1_lib.cc
@@ -2111,7 +2111,7 @@ // Predict the most preferred group. Span<const uint16_t> groups = tls1_get_grouplist(ssl); - if (groups.size() == 0) { + if (groups.empty()) { OPENSSL_PUT_ERROR(SSL, SSL_R_NO_GROUPS_SPECIFIED); return 0; } @@ -2290,7 +2290,7 @@ // https://tools.ietf.org/html/draft-ietf-tls-tls13-16#section-4.2.2 static int ext_cookie_add_clienthello(SSL_HANDSHAKE *hs, CBB *out) { - if (hs->cookie.size() == 0) { + if (hs->cookie.empty()) { return 1; } @@ -3184,7 +3184,7 @@ } Span<const uint16_t> peer_sigalgs = hs->peer_sigalgs; - if (peer_sigalgs.size() == 0 && ssl3_protocol_version(ssl) < TLS1_3_VERSION) { + if (peer_sigalgs.empty() && ssl3_protocol_version(ssl) < TLS1_3_VERSION) { // If the client didn't specify any signature_algorithms extension then // we can assume that it supports SHA1. See // http://tools.ietf.org/html/rfc5246#section-7.4.1.4.1