@[email protected]M to Fun Loops ▶️@midwest.socialEnglish • 2 months ago[R] Stupidest ways people have solved coding interviewsloops.videoexternal-linkmessage-square36fedilinkarrow-up182arrow-down15
arrow-up177arrow-down1external-link[R] Stupidest ways people have solved coding interviewsloops.video@[email protected]M to Fun Loops ▶️@midwest.socialEnglish • 2 months agomessage-square36fedilink
minus-square@[email protected]linkfedilink15•2 months agoIt doesn’t, the array is still in the same order it started in, it’s members are just printed to the console in numerical order. It just prints the number 1 after 1 ms, 2 after 2 ms, 3 after 3 ms etc.
minus-square@Randelunglink7•2 months agoInstead of print you could add them to a second array, though. Even clear the original first for “in place” sorting; never mind the memory allocation for the lambdas.
minus-square@Maaluslink2•2 months agoAlso since you aren’t guaranteed that there is a “happens before” relationship, it’s a wrong implementation that returns unsorted arrays in text too.
It doesn’t, the array is still in the same order it started in, it’s members are just printed to the console in numerical order.
It just prints the number 1 after 1 ms, 2 after 2 ms, 3 after 3 ms etc.
Instead of print you could add them to a second array, though. Even clear the original first for “in place” sorting; never mind the memory allocation for the lambdas.
Also since you aren’t guaranteed that there is a “happens before” relationship, it’s a wrong implementation that returns unsorted arrays in text too.