Re: Integer precision of function return types

[monkyyy via Digitalmars-d-learn]

On Thursday, 26 September 2024 at 06:53:12 UTC, Per Nordlöw wrote:
Should a function like
```d
uint parseHex(in char ch) pure nothrow @safe @nogc {
        switch (ch) {
        case '0': .. case '9':
                return ch - '0';
        case 'a': .. case 'f':
                return 10 + ch - 'a';
        case 'A': .. case 'F':
                return 10 + ch - 'A';
        default:
                assert(0, "Non-hexadecimal character");
        }
}
```

instead return an ubyte?

It will only matter if its stored; stack or the very probable 
inlining optimizations should just be as simple as possible so 
you dont confuse the optimizer