| commit | d290d2729d6afe62446789237a58ca87a6672405 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Tue Apr 08 12:53:55 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 08 12:54:52 2025 -0700 |
| tree | bce770e1183950b4c47e0d809dfad18d3641bcef | |
| parent | 003094a4b111ce922a71e109537577ed682a04f8 [diff] |
Comment out absl nullability macros when copying out from google3/. In some of the versions of absl that quiche is used with, the macros are uppercase; in others, the macros are lowercase, so until this is consistent, comment them out. This workaround will allow go/nullability-annotation-alias-to-macro-migration to proceed, without significant loss of verification of the annotations, which is done by an internal-only ClangTidy check in google3. This has no impact on code internally, and fixes the external build. PiperOrigin-RevId: 745256376
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.