Does the Mutex mechanism enforce a strict order for threads when accessing shared resources for reading and writing?

The Mutex mechanism in Go provides mutual exclusion when accessing shared resources, meaning it guarantees that only one goroutine can own the mutex and work with the resource at a given time.

However, Mutex does not guarantee strict order of thread access. If multiple goroutines are waiting for the mutex, the order in which they acquire the lock is not defined and depends on the scheduler.

If a strict order is required, for example, based on request time or priority, additional logic must be implemented, such as using channels or other synchronization primitives.