patternsresult-type
Result Type Pattern (C-Specific) pattern for C development
When & Why to Use This Skill
This Claude skill facilitates the implementation of the Result Type Pattern specifically for C development, providing a robust framework for explicit error handling. By utilizing a structured result type instead of traditional return codes, it ensures that errors are never ignored and provides a clear, exception-free mechanism for propagating error context throughout the application stack.
Use Cases
- Standardizing Error Handling: Implement a consistent 'res_t' structure across C libraries to ensure predictable and readable API behavior.
- Safe Error Propagation: Use the TRY and CHECK macros to cleanly bubble up errors through the call stack without deeply nested conditional logic.
- Preventing Silent Failures: Enforce a coding standard where callers must explicitly check the success status of a function, reducing bugs related to unhandled edge cases.
- Legacy Code Modernization: Refactor existing C codebases to replace inconsistent error-handling methods with a unified, modern Result pattern.
| name | patterns/result-type |
|---|---|
| description | Result Type Pattern (C-Specific) pattern for C development |
Result Type Pattern (C-Specific)
Return struct containing success/failure status plus value or error. Explicit error handling without exceptions. Caller must check result.
ikigai Application
Core type: res_t used throughout:
res_t result = ik_cfg_load(ctx, path, &cfg);
if (!result.ok) {
// Handle error, result.error contains message
}
Macros:
OK(value)- Construct success resultERR(msg)- Construct error resultTRY(expr)- Propagate error if failedCHECK(cond, msg)- Return error if condition false
Benefits:
- Errors can't be ignored (must check
.ok) - Error context propagates up call stack
- No hidden control flow (unlike exceptions)
See: project/error_handling.md for patterns.