In this case, depending upon what your use case is, you might be better off using int (or long long) for s1 and s2. There are some functions in c/posix that could/should use size_t, but don't because of … Here's a hint:

Yet, github reports the size as 0. So i'm assuming it only … In several c++ examples i see a use of the type size_t where i would have used a simple int. What's the difference, and why size_t should be better? If the size of the int is that important one can use int16_t, int32_t and int64_t (need the iostream include for that if i remember correctly). What's nice about this that int64_t should not have issues on a 32bit …

If the size of the int is that important one can use int16_t, int32_t and int64_t (need the iostream include for that if i remember correctly). What's nice about this that int64_t should not have issues on a 32bit …