Talk:Structured concurrency
| This is the talk page for discussing improvements to the Structured concurrency article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
"History" should not enumerate every implementation
> In 2021, Swift adopted structured concurrency. Later that year, a draft proposal was published to add structured concurrency to Java.
I think the point of the History section was to explain the origins of structured concurrency and cite contributors.
The citations for Swift and Java sound like implementations of what was already established. Perhaps there should be a separate section enumerating implementations. Lucenty (talk) 11:37, 3 September 2022 (UTC)
Structured concurrency has existed for at least 52 years
This article claims that structured concurrency was first proposed in 2016. It seems more accurate to say that structured concurrency is a very old idea that has had a recent resurgence in popularity.
Chapter 15 of the reference manual for PL/I (F), a programming language from 1972, presents a multitasking system where a task can spawn attached subtasks. And in particular:
> When a task is terminated, any of its subtasks that are still active are abnormally terminated.
Ada '83 has a similar feature. To quote the reference manual:
> If a task has dependent tasks, its termination takes place when the execution of the task is completed and all dependent tasks are terminated. A block statement or subprogram body whose execution is completed is not left until all of its dependent tasks are terminated.
This Wikipedia article doesn't mention any of this very similar prior work. This seems like a major oversight. 157.211.234.44 (talk) 06:15, 3 July 2024 (UTC)