Don't address introduce ambiguous locking order across attempts? While not obvio... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		Guvante 26 days ago \| parent \| context \| favorite \| on: Surelock: Deadlock-Free Mutexes for Rust Don't address introduce ambiguous locking order across attempts? While not obviously problematic, that seems weird enough you would need to validate that it is explicitly safe.

Seattle3503 26 days ago [–]

If I need to grab 100 locks, they are all moving around a lot, but I've got the first 10, will the order be the same for someome trying to get the same 100? Eg maybe someone swaps two that neither of us has grabbed yet.

Guvante 17 days ago | [–]

That makes sense you could only move locks that are "after" all taken locks

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact