arrow-typed-errors

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Classify the failure first: logical failure (typed error) vs exceptional failure (exception).
Pick the surface type:
- ```
Raise<E>
```
  + builder (
```
either {}
```
  /
```
option {}
```
  /
```
nullable {}
```
  ) for composable logic.
- Wrapper type (
```
Either
```
  /
```
Option
```
  /
```
Ior
```
  /
```
Result
```
  /nullable) for API boundaries.
Read
```
references/typed-errors.md
```
for API details and patterns before coding if unsure.

Smart constructors (parse, don't validate): make constructors private; expose
```
invoke
```
returning
```
Either
```
.
Validation accumulation: use
```
EitherNel
```
and
```
zipOrAccumulate
```
/
```
mapOrAccumulate
```
.
Wrapper choice:
- Prefer nullable for optional values unless nested nullability issues exist; then use
```
Option
```
  .
- Use
```
Either
```
  for disjoint success/failure;
```
Ior
```
  only when success + warning is meaningful.
- Use
```
Result
```
  only when errors are
```
Throwable
```
  and interop with stdlib APIs is required.
Error translation across layers: use
```
withError
```
to map inner errors to outer domain errors.
Drop error types explicitly: wrap
```
bind
```
with
```
ignoreErrors
```
when moving from informative error types to
```
Option
```
/nullable flows.
Avoid sealed-on-sealed inheritance: model error hierarchies with composition (wrapper data classes), not sealed inheritance chains.

智能构造函数（解析而非验证）：将构造函数设为私有；暴露返回
```
Either
```
的
```
invoke
```
方法。
验证累积：使用
```
EitherNel
```
和
```
zipOrAccumulate
```
/
```
mapOrAccumulate
```
。
包装类型选择：
- 优先使用可空类型表示可选值，除非存在嵌套可空性问题；此时使用
```
Option
```
  。
- 使用
```
Either
```
  表示互斥的成功/失败场景；仅当成功+警告有实际意义时使用
```
Ior
```
  。
- 仅当错误为
```
Throwable
```
  且需要与标准库API互操作时使用
```
Result
```
  。
跨层错误转换：使用
```
withError
```
将内部错误映射为外部领域错误。
显式丢弃错误类型：当从包含信息的错误类型切换到
```
Option
```
/可空类型流程时，用
```
ignoreErrors
```
包装
```
bind
```
。
避免密封类型的继承嵌套：使用组合（包装数据类）而非密封继承链来建模错误层级。

Load
```
references/typed-errors.md
```
for API details, error accumulation, wrapper-specific guidance, and sample snippets.