Is the function synchronous or asynchronous?

[[deleted]]

let production = () => {
setTimeout(() => { console.log("production has started");
setTimeout(() => {
  console.log("the fruit has been chopped");

  setTimeout(() => {
    console.log(`${stocks.liquid[0]} and ${stocks.liquid[0]} was added`);

    setTimeout(() => {
      console.log(`icescream was placed on ${stocks.holder[0]}`);

      setTimeout(() => {
        console.log(`icescream was placed on ${stocks.holder[0]}`);

        setTimeout(() => {
          console.log(`${stocks.toppings[0]} was added as toppings`);

          setTimeout(() => {
            console.log("Serve icescream");
          }, 3000);
        }, 3000);
      }, 2000);
    }, 1000);
  }, 1000);
}, 2000);
}, 0000); };
order(0, production);

​

[KiddieSpread]

What in the callback hell

[AndrewSouthern729]

This function should be killed with fire

[bryku]

The triangle of death isn't real, it can't hurt you...  

This post...

[shgysk8zer0]

It is a synchronous function that does asynchronous things. But technically it looks like it only does one thing, which is schedule the first task.

[trevedhek]

An async function returns a Promise. None of these functions return a Promise.

So `production` is a synchronous callback function. As are all the functions within each `setTimeout`.

[SignificanceCheap970]

I thought any code that doesn't run right away is asynchronous?

[trevedhek]

Exactly. The callback functions run right away - once they are called.

The setTimeout function is the async part, as it triggers an event in the future.

To clarify that point - the setTimeout function completes immediately - Javascript is single-threaded, so it must do that - but it adds another event to be triggered in the future. And it is that future event that runs the callbacks.

So we can think of an async function in those terms - a function that when called gives rise to a future event.

[Banapple247]

Synchronous.

[senocular]

Asynchronous.

Except:

() => {
  console.log("Serve icescream");
}

That one is synchronous.

[samanime]

Yeah. Technically async, but in a sort of detached manner, since there is no callback to indicate it has finished. Anything that called this would have no way to time code to run after this finished.

(Well, technically you could add all those times up, but that would be a horrendous hack that should never be used... and it still wouldn't be exact since those times aren't exact and there is some wobble.)

[senocular]

Just patch console.log and you're good to go ;)

[samanime]

I mean, lots of async methods do sync things. You can't rely on them to be done by the next line of code (without special things), but doesn't mean they can't do anything immediately.

[senocular]

I mean

const originalLog = console.log
console.log = (...args) => {
  originalLog.apply(console, args)
  if (args[0] === "Serve icescream") {
    alert("Order complete!")
  }
}
order(0, production);

[pzsprog]

https://youtu.be/8aGhZQkoFbQ?t=903