Is this bad practice with static classes and thread safety?

Question

Assuming I'm not using a lock statement, is this bad practice?

public static class Foo
{
  public static string Bar()
  {
    bool working;

    while (working)
    {
      // Loop until ready to run.
    }

    working = true;

    // Do stuff here.

    working = false;
    return "done."
  }
}

Edit -

Having tried something like this, I understand that this is not possible for several reasons. I was just curious. The example I wrote does not even work.

Answer 1

Loop is the process of consuming a processor.

I mean, everything you do is just waiting. This is not good.

Answer 2

-, , . 2 , , "". , .

. 2 , () , working = true; .

.

Answer 3

, , working , :

• volatile static. Volatile , "" .

• " ". , . , , ​​ working.

Answer 4

, .

? Monitor, .

- .

Answer 5

: ( , ), , , . , ​​ " ", , System.Threading.Thread.MemoryBarrier.

But you should use locks instead. Free programming is incredibly difficult to get right.

Answer 6

Using locks is the only way to prevent concurrency problems (others that don't).

public static class Foo
{
  private static object barLock = new object();

  public static string Bar()
  {
    lock (barLock)
    {
      // Do work
      return "Done";
    }
  }
}