> I don't want to handle errors after every division and division doesn't crash. You can have one or the other. You can't have both without the risk of nasal

> I don't want to handle errors after every division and division doesn't crash. You can have one or the other. You can't have both without the risk of nasal demons. Unless the result of the operation is business-safe to throw away. That's why having the default / have both is an poor design choice by gleam and pony. Someone will reach for / and encounter demons. Afaict the other langs that do this are not intended for real world prod use. By default / should force the developer into either crashable or unwrap error return. If you want some sort of opt-in "logic-unsafe /", fine but call it something else like </> e.g.