[synchronization] spinlocks

[ZackyGameDev]

Need to implement spinlocks.

There is creative liberty on how to do it.

I myself don't know a lot about spinlocks a whole lot so need to read up and study on that a bit. And need to determine if we even need them.

[tanishqdaiya]

We are definitely going to use locks extensively in many shared data structures. There's three stages to it

1. Try: It will try to acquire the lock
2. Loop: If the lock is already acquired, it will wait (and waste cpu cycles but for our intents and purposes, we will bite that bullet)
3. Acquire: If the lock is released, it will try to acquire it.

Acquire will be an atomic operation so that other threads don't simultaneously acquire the same resource.

I can work on an implementation that suits the needs.

[ZackyGameDev]

I looked into it and it appears that spinlocks are mainly used in multi-core systems. Since we have a single core running so far, it might not be very productive to implement it. Mutex locks may be a better idea to implement.

[tanishqdaiya]

Writing a spin-lock would not interfere with the mutex but rather make it easier to implement a mutex lock. The spin-lock will set up the very foundation for mutexes.

I assign myself to this.

[ZackyGameDev]

solved by PR #12