Skip to content

Commit e88205c

Browse files
stage 1 🎉
1 parent ce98671 commit e88205c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
JavaScript Concurrency Control Proposal
22
=======================================
33

4-
**Stage:** 0
4+
**Stage:** 1
55

66
**Champions:** Michael Ficarra, Luca Casonato
77

@@ -153,4 +153,4 @@ While a semaphore is a common concurrency control mechanism, there are many othe
153153

154154
Because of this variety of use cases, it is important to give developers the flexibility to use their own concurrency control mechanisms with built in JavaScript APIs.
155155

156-
The `Semaphore` class provides a simple and common concurrency control mechanism that can be used in many cases. It is expected that many developers will use `Semaphore` for their concurrency control needs. However, because APIs don't explicitly take a `Semaphore` instance, but any object that implements the `Governor` interface, developers can use their own concurrency control mechanisms if they need to.
156+
The `Semaphore` class provides a simple and common concurrency control mechanism that can be used in many cases. It is expected that many developers will use `Semaphore` for their concurrency control needs. However, because APIs don't explicitly take a `Semaphore` instance, but any object that implements the `Governor` interface, developers can use their own concurrency control mechanisms if they need to.

0 commit comments

Comments
 (0)