I think I had a similar problem a similar problem with printing some time ago... Anyway: use BiggestUInt instead of uint64. It has better semantics and could be platform-adjusted, e.g. we could add uint128 if there was a platform which natively supports it and the BiggestInt would then be uint128.
- Getting ambiguous call on $(range) and idk why monster
- Re: Getting ambiguous call on $(range) and idk why cdome
- Re: Getting ambiguous call on $(range) and idk why monster
- Re: Getting ambiguous call on $(range) and idk w... Udiknedormin
