RemoveChars(input, base::as_string_view(kInfraAsciiWhitespace),Tom SepezI'm fine with this as a straighforward conversion, but it seems like there's some future room for simplification, e.g. can't this just be `RemoveChars(input, kInfraAsciiWhitespace))`?
Yeah, removeChars should take a span of chars as its second arg. Later.
// Note 1: using as_string_view() or span() can cause issues with constexprTom SepezNit: remove this
Done
base::as_string_view(base::as_byte_span(new_path.value()));Tom Sepez... this is extremely suspect and seems like this should just be passing around a byte span.
Maybe we can just fix `GenerateId()` in this CL?
Split into separate CL.
return Base64UrlEncode(base::as_string_view(data));Tom SepezMaybe this should just pass a byte span through to line 50?
Done. Actually just calls alternate API in same manner as 52
return base::as_string_view(kSslClientHello);Tom SepezI guess this is fine, but I have to admit that the overlap between `base::as_string_view()` and `base::MakeStringViewWithNulChars()` doesn't seem the best; should we be trying to fix that at some point?
Yeah, not sure what the right thing is. Note that WithNulChars omits trailing nul.
auto key_string = base::as_string_view(key);
auto value_string = base::as_string_view(value);Tom SepezDo we need these at all?
Nope.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |