Me: ++i;
Friend: i++;
Sad story 😂

But there is a difference...

@hubiruchi I know, ++i is more efficient because i++ makes copy ... xD

@vukdev not only that. ++i return the value of i after increment, and i++ return the value before the incrememt

@hubiruchi Yes, but there is always a person who will write i++

I always use i++ what you talking about

@hubiruchi I don't think he knew.

Are you suggesting: for (int i = -1; i < x; ++i)?

@devTea ++i will increment the value of i, and then return the incremented value and i++ will increment the value of i, but return the original value

@spongessuck Yes

Ok this is strange tbh, I mean returns a copy, but that helps for embedded systems where every byte counts

i would be surprised if the compiler wouldn't optimized this and even directly stripped out the return value if not needed.

To @gitpush: In embedded systems where every byte counts you are gonna use assembly! No need to include all of that libc bloat! (even tho you can probably somehow compile without it)

@gitreflog tbh I'm not an embedded system dev nor I have info about it, but you have a point in what you said also about the part where compiler strips out non needed return value, though imo it is good for people to know the difference till that much and not like ++i adds then return and i++ return then add

I wanted to point out the folliwing:
++i != i++

But then I realized that actually false

@Awlex but i++ != ++i

@gitreflog Embedded compiling without libc is easy - just don't use its functions.

But assembly is gone in embedded, there is enough memory for C. The dev times are much shorter, that's why.

++i ftw!