Uses constexpr to improve header validation code generation. Thank you to ricea@google.com for the suggestion!

```
$ benchy --perflab --reference=srcfs //third_party/http2/adapter:header_validator_benchmark

(Generated by http://go/benchy. Settings: --runs 5 --reference "srcfs" --perflab)

name                                  old cpu/op   new cpu/op   delta
BM_ValidateSingleHeaderForRequests    527ns ± 3%   408ns ± 1%  -22.64%  (p=0.016 n=5+4)
BM_ValidateSingleHeaderForResponses   818ns ±17%   628ns ± 3%  -23.23%  (p=0.008 n=5+5)

name                                  old time/op             new time/op             delta
BM_ValidateSingleHeaderForRequests    528ns ± 3%              409ns ± 1%  -22.65%          (p=0.016 n=5+4)
BM_ValidateSingleHeaderForResponses   821ns ±17%              630ns ± 3%  -23.28%          (p=0.008 n=5+5)

name                                  old INSTRUCTIONS/op     new INSTRUCTIONS/op     delta
BM_ValidateSingleHeaderForRequests    5.75k ± 0%              4.69k ± 0%  -18.50%          (p=0.008 n=5+5)
BM_ValidateSingleHeaderForResponses   8.21k ± 0%              6.72k ± 0%  -18.19%          (p=0.008 n=5+5)

name                                  old CYCLES/op           new CYCLES/op           delta
BM_ValidateSingleHeaderForRequests    1.73k ± 0%              1.32k ± 1%  -23.81%          (p=0.008 n=5+5)
BM_ValidateSingleHeaderForResponses   2.59k ± 1%              2.01k ± 0%  -22.42%          (p=0.008 n=5+5)

name                                  old allocs/op           new allocs/op           delta
BM_ValidateSingleHeaderForResponses    1.00 ± 0%               1.00 ± 0%     ~     (all samples are equal)

name                                  old peak-mem(Bytes)/op  new peak-mem(Bytes)/op  delta
BM_ValidateSingleHeaderForResponses    32.0 ± 0%               32.0 ± 0%     ~     (all samples are equal)

Results uploaded to http://sponge2/818994d8-6ad4-4dce-ad8f-42319ec5f962
```

PiperOrigin-RevId: 601176797
1 file changed
tree: 34750cd8159bdb19b60181165699d29cd99f9537
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. .bazelversion
  6. BUILD.bazel
  7. CONTRIBUTING.md
  8. LICENSE
  9. README.md
  10. WHITESPACE
  11. WORKSPACE.bazel
README.md

QUICHE

QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.

There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:

To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:

To contribute to QUICHE, follow instructions at CONTRIBUTING.md.

QUICHE is only supported on little-endian platforms.