| commit | 7ad884df70f74732146abc647f2ff0adc1925418 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Wed Apr 13 13:13:31 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 13 13:15:06 2022 -0700 |
| tree | 15f81ebc0afd1601959f982f4e2f408510627dbd | |
| parent | 76b4daecf4b88a7a6eb48bea49a7d5f9f4853939 [diff] |
Remove VERIFY_AND_RETURN_SUCCESS. This is a non-standard macro that calls VERIFY_SUCCESS then returns AssertionSuccess. The same result can be achieved by simply returning its argument. The only change is that VERIFY_SUCCESS logs the location of this macro upon failure, but given that every macro that potentially generates an AssertionFailure (like VERIFY_EQ or VERIFY_FALSE) already logs the location of the failure itself, there is not much value in this intermediate location. PiperOrigin-RevId: 441560319
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.