Sha256: 3ed34cb32f08f2f96b51d11e8fda5639640f76f47c5350be7ea4d28e8d68448f
Contents?: true
Size: 565 Bytes
Versions: 2
Compression:
Stored size: 565 Bytes
Contents
# RFC: Consistent error handling * **Authors**: - * **Date**: - * **Status**: Draft ## Abstract Error handling in the H3 library is inconsistent across functions, many of which have no explicit mechanism to indicate that an error occured. This RFC proposes updating all functions that allocate blocks of memory or that could receive invalid input to return an integer code indicating success or error. ## Motivation *Why is this important?* ## Approaches *What are the various options to address this issue?* ## Proposal *What is the recommended approach?*
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
h3-3.7.2 | ext/h3/src/dev-docs/RFCs/v4.0.0/error-handling-rfc.md |
h3-3.7.1 | ext/h3/src/dev-docs/RFCs/v4.0.0/error-handling-rfc.md |