4 ms·

In the repeater callback, you're both calling the stop argument and awaiting it. Is it somehow both a function and a promise? Is this possible in JS? edit: I f

• bikeshaving 8mo ago
  Yes, the callable promise abstraction is just a bit of effort: let resolveRef; const promise = new Promise((res) => { resolveRef = res; }); const callback = (data) => { // Do work... resolveRef(data); // This "triggers" the await }; Object.assign(callback, promise); There’s a real performance cost to awaiting a fake Promise though, like `await regularPromise` bypasses the actual thenable stuff.
• sheept 8mo ago
  It's not common, but there are web APIs where you await a promise that already exists as a property, rather than being returned from a function call, like await document.fonts.ready device.lost.then(() => { console.log('WebGPU device lost :(') }) I feel like this isn't confusing if you know how promises work, but maybe it can be confusing for someone coming from Python/Rust, where async functions don't evaluate until their futures are awaited.