처리하다 catch
Provenance
- #21 errors-exceptions concept_map maps javascript/catch → concept catch
- #23 demo-alpha concept_map maps javascript/catch → concept catch
- #28 sealion-refinement concept_map maps javascript/catch → concept catch winning layer
Full per-leaf change history across brain builds is not yet recorded; shown is the current build's layer stack.
Across locales
What each covering migration carries for this concept, per locale — the whole-brain view, not filtered by your language. Forms are the migration's leaf values (pre-transform, pre-human-verdict); a locale without a form falls back to canonical English. Chips open that locale's live docs page for this term.
errors-exceptions · concept catch — per-locale forms
Expand to load the per-locale matrix.
demo-alpha · concept catch — per-locale forms
Expand to load the per-locale matrix.
sealion-refinement · concept catch — per-locale forms
Expand to load the per-locale matrix.
AI council review
Reviewed by 1 model
· @cf/aisingapore/gemma-sea-lion-v4-27b-it · 2026-07-17
Cluster errors-exceptions
· locale ko-Hani
· member catch
'처리하다' (cheori-hada) better conveys the idea of handling an exception in a programming context. It's more natural than '捕捉'.
Issue breakdown
- specificity While '捕捉' means 'catch', it feels more like physically catching something. In exception handling, '처리하다' (process/handle) or '수집하다' (collect) might be more appropriate.
- consistency Collapsed with except/rescue, which is reasonable, but the base term could be better.