Return to Question

I have not found many resources about this: I was wondering if it's possible/a good idea to be able to write asynchronous code in a synchronous way.

For example, here is some Javascript code which retrieves the number of users stored in a database (an asynchronous operation):

getNbOfUsers(function (nbOfUsers) { console.log(nbOfUsers) });

It would be nice to be able to write something like this:

const nbOfUsers = getNbOfUsers();
console.log(getNbOfUsers);

And so the compiler would automatically take care of waiting for the response and then execute console.log. It will always wait for the asynchronous operations to complete before the results have to be used anywhere else. We would make so much less use of callbacks promises, async/await or whatever, and would never have to worry whether the result of an operation is available immediately or not.

Errors would still be manageable (did nbOfUsers get an integer or an error?) using try/catch, or something like optionals like in the Swift language.

Is it possible? It may be a terrible idea/a utopia... I don't know

I have not found many resources about this: I was wondering if it's possible/a good idea to be able to write asynchronous code in a synchronous way.

For example, here is some JavaScript code which retrieves the number of users stored in a database (an asynchronous operation):

getNbOfUsers(function (nbOfUsers) { console.log(nbOfUsers) });

It would be nice to be able to write something like this:

const nbOfUsers = getNbOfUsers();
console.log(getNbOfUsers);

And so the compiler would automatically take care of waiting for the response and then execute console.log. It will always wait for the asynchronous operations to complete before the results have to be used anywhere else. We would make so much less use of callbacks promises, async/await or whatever, and would never have to worry whether the result of an operation is available immediately or not.

Errors would still be manageable (did nbOfUsers get an integer or an error?) using try/catch, or something like optionals like in the Swift language.

Is it possible? It may be a terrible idea/a utopia... I don't know.

I did not find many resources about this, I was wondering if it's possible/a good idea to be able to write asynchronous code in a synchronous way.

For example here is a javascript code which retrieves the number of users stored in a database (asynchronous operation):

getNbOfUsers(function (nbOfUsers) { console.log(nbOfUsers) });

It would be nice to be able to write something like that:

const nbOfUsers = getNbOfUsers();
console.log(getNbOfUsers);

And so the compilator would automatically take care of waiting for the response to then execute console.log. It will always wait for the asynchronous operations to answer before the results have to be used anywhere else. We would use so much less often callbacks, promises, async/await or whatever, and never have to worry if the result of an operation is available immediately or not.

Errors would still be manageable (does nbOfUsers got an integer or an error?) using try/catch, or something like optionals like in Swift language.

Is it possible? It may be a terrible idea/a utopia... I don't know

I have not found many resources about this: I was wondering if it's possible/a good idea to be able to write asynchronous code in a synchronous way.

For example, here is some Javascript code which retrieves the number of users stored in a database (an asynchronous operation):

getNbOfUsers(function (nbOfUsers) { console.log(nbOfUsers) });

It would be nice to be able to write something like this:

const nbOfUsers = getNbOfUsers();
console.log(getNbOfUsers);

And so the compiler would automatically take care of waiting for the response and then execute console.log. It will always wait for the asynchronous operations to complete before the results have to be used anywhere else. We would make so much less use of callbacks promises, async/await or whatever, and would never have to worry whether the result of an operation is available immediately or not.

Errors would still be manageable (did nbOfUsers get an integer or an error?) using try/catch, or something like optionals like in the Swift language.

Is it possible? It may be a terrible idea/a utopia... I don't know

I did not find much ressources about this, i was wondering if it's possible/a good idea to be able to write asynchronous code in a synchronous way.

For example here is a javascript code which retrieve the number of users stored in a database (asynchronous operation):

getNbOfUsers(function (nbOfUsers) { console.log(nbOfUsers) });

It would be nice to be able to write something like that:

const nbOfUsers = getNbOfUsers();
console.log(getNbOfUsers);

And so the compilator would automatically take care of waiting the response to then execute console.log. It will always wait for the asynchronous operations to answer before the results have to be used anywhere else. We would use so much less often callbacks, promises, async/await or whatever, and never have to worry if the result of an operation is available immediately or not.

Errors would still be manageable (does nbOfUsers got an integer or an error?) using try/catch, or something like optionals like in Swift language.

Is is possible? It may be a terrible idea/an utopia... i don't know

I did not find many resources about this, I was wondering if it's possible/a good idea to be able to write asynchronous code in a synchronous way.

For example here is a javascript code which retrieves the number of users stored in a database (asynchronous operation):

getNbOfUsers(function (nbOfUsers) { console.log(nbOfUsers) });

It would be nice to be able to write something like that:

const nbOfUsers = getNbOfUsers();
console.log(getNbOfUsers);

And so the compilator would automatically take care of waiting for the response to then execute console.log. It will always wait for the asynchronous operations to answer before the results have to be used anywhere else. We would use so much less often callbacks, promises, async/await or whatever, and never have to worry if the result of an operation is available immediately or not.

Errors would still be manageable (does nbOfUsers got an integer or an error?) using try/catch, or something like optionals like in Swift language.

Is it possible? It may be a terrible idea/a utopia... I don't know