Nickolay Bukreyev

Results 19 issues of Nickolay Bukreyev

https://github.com/status-im/nim-chronos/blob/f3b77d86615813690c5ab5e7cbe841521be2a20f/chronos/asyncmacro2.nim#L126-L133 If you take the body of a procedure after it is processed by `.async`, put it into a new procedure, and apply `.async` to it, `chronosInternalRetFuture` will refer to...

```d auto myBold = bold; assert(is(typeof(myBold("text")) == string)); assert(!is(typeof(bold("text")): string)); // Not even convertible. ``` (That’s because `bold()("text")` returns `string` while `bold("text")` returns `StyledText`.) IMHO, it shouldn’t work like this....

Discovered this when I was trying to deduplicate `Complete.InitCmd`. A reduced example that should be easier to follow: ```d struct Description { string delegate() dg; } auto createCompleter(string desc) {...

bug

Fix: `dub test --build=unittest-cov-ctfe --verbose`. https://dub.pm/package-format-sdl.html#build-types

wontfix

I think, apart from being case-sensitive or case-insensitive, there is a third practically useful approach: ignore case in long options but be case-sensitive in short ones. The reason is that...

enhancement

An example from the Readme, reduced: ```d import argparse; struct T { @(PositionalArgument(0).Description(() => "Argument description")) string param0; } void main() { CLI!T.parseArgs!((T t) { })(["-h"]); // SIGILL } ```...

Currently, if a parsing error occurs, the program exits with code *1*; this is hard-coded into the library. However, the program may want to use return code *1* itself and...

enhancement

I’m almost satisfied with the way `argparse` formats the help message. Just a couple of suggestions: 1. `-h`/`--help` argument should be customizable. For example, one might want to reword its...

enhancement

```d struct S { string s; } @safe: string test1(scope S* p) => p.s; // OK. string test2(scope S* p) => __traits(child, p, S.s); // Error. string test3(scope S* p)...