jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Improve exception usage in parseutils (#10284)

Browse source
This commit is contained in:
Oscar Nihlgård 2019-01-15 23:48:19 +01:00 • committed by Andreas Rumpf
commit 1d7e3a84fd
2 changed files with 34 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

2
changelog.md
View file

@ -36,6 +36,8 @@
- `system.ValueError` now inherits from `system.CatchableError` instead of `system.Defect`.
- The procs `parseutils.parseBiggsetInt`, `parseutils.parseInt`, `parseutils.parseBiggestUInt` and `parseutils.parseUInt` now raise a `ValueError` when the parsed integer is outside of the valid range. Previously they sometimes raised a `OverflowError` and sometimes returned `0`.
- nre's `RegexMatch.{captureBounds,captures}[]` no longer return `Option` or
`nil`/`""`, respectivly. Use the newly added `n in p.captures` method to
check if a group is captured, otherwise you'll recieve an exception.