This is the current revision of this page, as edited by Klbrain(talk | contribs) at 12:06, 17 June 2025(Adding {{merged-to|Event (computing)#Event semaphore}} (easy-merge)). The present address (URL) is a permanent link to this version.Revision as of 12:06, 17 June 2025 by Klbrain(talk | contribs)(Adding {{merged-to|Event (computing)#Event semaphore}} (easy-merge))
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.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
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?
