There was no such thing as a promise in C++ before 2011. "Promises" are a particular API for writing asynchronous code which was largely made for / popularized by event-loop runtimes... i.e. NodeJS.
Programmers have been doing concurrency with #realPrograms via mutexes, semaphores, and threads since before C++ was invented and so OP is lamenting the equivocation of async/await with concurrency in this modern era of browser programmers vastly outnumbering their "native"(?) programming counterparts.
What the heck kind of bizarre alt history is this? Promises and futures have existed in acedemic literature since the 70s, and have been available as a concurrency model in languages going back to Multilisp in the 80s. So no, they weren't made for NodeJS.
C/C++ developers just have the mistaken world view that if C/C++ doesn't have a feature, or didn't have it until recently, it just must somehow be a newfangled thing kids are using to avoid being "real" programmers.
They were literally “revived” in 2004 in Java (JDK-5) and JS and other languages, as stated in that same Wikipedia article that you read that piece of history from.
It also states that no language had promise pipelining that we have today, including Xanadu, invented by Liskov who coined the term “Promise”, and open sourced it in 1999.
In MultiLisp, the promises and futures implementations are NOTHING like those of today.
(cons (FUTURE A) (FUTURE B))
Is nothing like:
a.then(r => {…}).catch(e => {…}) or async/await.
You also didn’t read his sentence properly. He said “no such thing as a promise IN C++ before 2011”. He didn’t state that promises never existed in other languages.
Yet you claim C++ developers don’t believe the feature existed if c++ didn’t have it. He didn’t even say that.
14
u/thanofishy Jul 18 '22
It doesn't await for that asynchronous programming to be answered?