cangjie-error-handle

You implement error handling in Cangjie using try/catch/finally blocks and try-with-resources for cleanup. CatchPattern structures allow you to intercept specific exceptions, while finally blocks guarantee resource cleanup during application workflows.

In Cangjie, Error and Exception separate internal system errors from logic errors. You should inherit custom classes from Exception for application logic failures, but not from Error, which is reserved for internal system-level failures.

To define custom exceptions in Cangjie, you extend the open class Exception using inheritance. This approach follows the allowed rules for extending Exception, enabling you to create specific exception types tailored to your application's logic failures.

Option-based error handling in Cangjie uses Option<T> with match, ??, ?, and getOrThrow() to safely manage missing values. This pattern provides an alternative to exceptions for controlling flow when optional data might be absent.

Try-with-resources in Cangjie ensures automatic resource cleanup when handling exceptions. By wrapping resource initialization within this control flow pattern, you guarantee that resources are safely released even if logic errors or failures occur.