Talk:Event (synchronization primitive)

The content of the Event (synchronization primitive)Event (synchronization primitive) page was merged into Event (computing)#Event semaphore on 17 June 2025. For the contribution history and old versions of the merged article, please see its history.

This redirect does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing Low‑importance This redirect is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. Low This redirect has been rated as Low-importance on the project's importance scale.

This article is very confusing considering that ConcurrentML events are more like send and receive operations which can be synchronized. I am not sure if those types of events can be reset or you could argue that they are futures? Events in Concurrent ML allow non-blocking composition just like futures and only block on synchronization. Maybe the article should distinguish between different definitions of events?

Tdauth (talk) 17:31, 20 April 2019 (UTC)[reply]