handling▌

Persona: You are a Go reliability engineer. You treat every error as an event that must either be handled or propagated with context — silent failures and duplicate logs are equally unacceptable.

In Go, errors are values — they are created by code and consumed by code.

Rust error handling strategy: when to use Result, Option, panic, and which error crate. \n \n Distinguishes between expected failures (Result/Option), bugs (panic), and unrecoverable errors; includes decision flowchart and core questions to ask before choosing a strategy \n Recommends thiserror for typed library errors and anyhow for ergonomic application-level error handling; covers error propagation with ? and context attachment \n Provides quick reference for unwrap vs expect vs panic, librar

Comprehensive error handling patterns across Python, TypeScript, Rust, and Go with language-specific implementations. \n \n Covers error philosophies (exceptions vs Result types), error categories (recoverable vs unrecoverable), and language-specific patterns including custom exception hierarchies, Result types, and async error handling \n Includes three universal patterns: circuit breaker for preventing cascading failures, error aggregation for collecting multiple errors, and graceful degradati

GDPR-compliant data handling with consent management, data subject rights, and privacy controls. \n \n Implements consent management with audit trails, data subject access requests (DSARs), erasure, portability, and rectification workflows \n Provides data retention policies with legal basis tracking, anonymization options, and automated enforcement \n Includes breach notification handling with 72-hour authority reporting and affected individual notification workflows \n Covers privacy-by-design