lit

Here I'd like to give more details to offer a little references: (in the case that I may not be able to spare time later) To begin with, I compiled...

> I find... > > - Any procedure that's related to parse some integers handles underline `_` (e.g. `parseOct`/`parseHex` [^1] ) > - `parseInt` `parseBiggestInt` handles leading sign character `+`/`-`....

> - Or just reflect these in runnableExamples as they used to do. Currently I've added examples for all `parseInt/parseBiggestInt` variants in `std/parseutils`

ping @ringabout

@ringabout any improvement needed? --- If such a feature is really required to be metioned in doc comment, not only runnableExamples, then I'll update all doc of these procs metioned...

Currently `void` is only valid for generic argument, function return type, etc, but not for any concrete type. As a variable of `void` is invalid, an array of `void` cannot...

> `### Expected Output` And > `### Possible Solution` These block formats are ill-formatted. --- ## culprit ### sort `sort` uses `system.cmp` by default. When either of its operands is...

> strm.write "" VM was tended to support write but in fact doesn't. `write` invokes `writeData` `whenvm`, which invokes `writeDataImpl` field. But that field was skipped to initialized [^impl], thus...

> ```Looking at python (yes again) "int" function: it does restrict to base 10 it doesn't work with weird japanese numerals coded on multiple codepoints (altough isnumeric returns yes) but...

> The signature should be IMO: > > ```nim > > func extractDigit*(r: Rune): Option[range[0..9]] > > ``` > > And it should support Unicode Digits. Correctly, I'm inspecting Python...