Thread overview
Unexpected result with std.conv.to
Nov 15, 2019
Joel
Nov 15, 2019
Jon Degenhardt
Nov 15, 2019
Joel
November 15, 2019
I made a feature that converts, say, [9:59am] -> [10:00am] to 1 minute. but found '9'.to!int = 57 (not 9).

Doesn't seem right... I'm guessing that's standard though, same with ldc.
November 15, 2019
On Friday, 15 November 2019 at 03:51:04 UTC, Joel wrote:
> I made a feature that converts, say, [9:59am] -> [10:00am] to 1 minute. but found '9'.to!int = 57 (not 9).
>
> Doesn't seem right... I'm guessing that's standard though, same with ldc.

Use a string or char[] array. e.g. writeln("9".to!int) => 9.

With a single 'char' what is being produced is the ascii value of the character.
November 15, 2019
On Friday, 15 November 2019 at 04:26:58 UTC, Jon Degenhardt wrote:
> On Friday, 15 November 2019 at 03:51:04 UTC, Joel wrote:
>> I made a feature that converts, say, [9:59am] -> [10:00am] to 1 minute. but found '9'.to!int = 57 (not 9).
>>
>> Doesn't seem right... I'm guessing that's standard though, same with ldc.
>
> Use a string or char[] array. e.g. writeln("9".to!int) => 9.
>
> With a single 'char' what is being produced is the ascii value of the character.

Thanks, Jon Degenhardt. I did work it out.