A modern programming language that makes developers happier.

kotlinlang

Hi guys! I've noticed that in latest Compose alpha compositeHashKey length was increased from 32 bits to 64 (on JVM). It was done to reduce chance of hash collisions. I'm just curious, what happens with Compose runtime if hash collision happens? I've never noticed any weird behavior causes by this, and hash length increase probably causes some runtime overhead, so there must be a reason to do this change which I'm curious to know :)

I don't think there's any runtime overhead, 64 bit CPUs are very good at handling 64 bit numbers

I think the chance of collision was decently high, but we didn't get any report of rememberSaveable missing data (which would happen in this case)

I see, it's indeed something not really noticeable, but good to hear that this bug will have much less chance now. Thank you!