size_t for length on x64 will make app slower than on x86?

[Matthias Bentrup via Digitalmars-d]

On Tuesday, 18 November 2014 at 07:04:50 UTC, FrankLike wrote:
>
>> Don't profile with out optimzation.
>> Add "-O -inline -release -boundscheck=off" to your dmd 
>> arguments.
>
> I mean projects moved from x86 to x64, 'cast(int)length ' is 
> better than 'size_t i=(something).length '.

I think the reason for the existence of size_t, is that the C 
designers thought that the second way is better than the first 
way.