| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Error -> Defect for defects (#13908) | Jacek Sieka | 2020-04-28 | 1 | -5/+5 |
| | | | | | | | | | | | | | | | * Error -> Defect for defects The distinction between Error and Defect is subjective, context-dependent and somewhat arbitrary, so when looking at an exception, it's hard to guess what it is - this happens often when looking at a `raises` list _without_ opening the corresponding definition and digging through layers of inheritance. With the help of a little consistency in naming, it's at least possible to start disentangling the two error types and the standard lib can set a good example here. | ||||
| * | Implements RFCs #209 (#13995) | cooldome | 2020-04-16 | 1 | -7/+3 |
| | | | | | | * add test * add changelod entry Co-authored-by: cooldome <ariabushenko@bk.ru> | ||||
| * | catchable defects (#13626) | Andreas Rumpf | 2020-03-12 | 1 | -0/+52 |
| * allow defects to be caught even for --exceptions:goto (WIP) * implemented the new --panics:on|off switch; refs https://github.com/nim-lang/RFCs/issues/180 * new implementation for integer overflow checking * produce a warning if a user-defined exception type inherits from Exception directly * applied Timothee's suggestions; improved the documentation and replace the term 'checked runtime check' by 'panic' * fixes #13627 * don't inherit from Exception directly | |||||