Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request undertakes a significant refactoring of the server example's error handling mechanism. By migrating from integer-based error codes to std::expected, the codebase now benefits from explicit and type-safe error propagation. This change enhances readability and maintainability by clearly distinguishing between successful outcomes and various failure modes, which are now precisely defined by an extended Error enum. The refactor touches a broad range of functions, ensuring a consistent and robust error management strategy.

Highlights

• Error Handling Refactor: Replaced traditional integer-based error codes with std::expected<T, Error> across numerous functions in the server example, providing a more modern and type-safe approach to error propagation.
• Expanded Error Enum: Introduced new Error enum values in shared.h to precisely categorize various failure conditions, including system calls, library errors (LIBC, HTTP3, QUIC), network states (SEND_BLOCKED, CLOSE_WAIT, RETRY_CONN, DROP_CONN), and token validation issues (UNREADABLE_TOKEN).
• Consistent Error Propagation: Updated error checking logic from if (rv != 0) or switch statements to if (!rv) and rv.error() for std::expected return types, standardizing error flow throughout the codebase.
• Function Signature Updates: Modified the return types of over 30 functions in Handler and Server classes from int to std::expected<void, Error>, std::expected<int, Error>, or std::span<const uint8_t> to align with the new error handling paradigm.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.