I've been working on implementing Java async/await state machine with switch statements and a scheduling loop. If the user doesn't await the async task handle, then the task's returnvalue is never handled. This is similar to the Go problem with the go statement.
If your async call returns a handle and
the handle is linked to a scope then in theory the async/await could be used as primitive to structured concurrency.
I journal about asynchrony and parallelism everyday in ideas4 (see my HN profile)
If you found this interesting then you shall like the following pages:
The Vale language blog post on seamless structured concurrency https://verdagon.dev/blog/seamless-fearless-structured-concu...
The rust book on concurrency https://doc.rust-lang.org/book/ch16-00-concurrency.html
I've been working on implementing Java async/await state machine with switch statements and a scheduling loop. If the user doesn't await the async task handle, then the task's returnvalue is never handled. This is similar to the Go problem with the go statement.
https://github.com/samsquire/multiversion-concurrency-contro...
If your async call returns a handle and the handle is linked to a scope then in theory the async/await could be used as primitive to structured concurrency.
I journal about asynchrony and parallelism everyday in ideas4 (see my HN profile)