Skip to content

CU-et6b7a Deprecate ConcurrentVar#2254

Merged
nomisRev merged 2 commits into
masterfrom
cu-et6b7a-deprecate-concurrentvar
Feb 25, 2021
Merged

CU-et6b7a Deprecate ConcurrentVar#2254
nomisRev merged 2 commits into
masterfrom
cu-et6b7a-deprecate-concurrentvar

Conversation

@nomisRev
Copy link
Copy Markdown
Member

ConcurrentVar has the same semantics as Channel(1), which is a Channel with the size for a single element. So it can also be empty or filled and it provides suspending semantics upon send and receive, it covers more use-cases as ConcurrentVar does.

@nomisRev nomisRev requested a review from a team February 25, 2021 11:06
@franciscodr
Copy link
Copy Markdown
Collaborator

Copy link
Copy Markdown
Member

@rachelcarmena rachelcarmena left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@nomisRev nomisRev merged commit 17b3b69 into master Feb 25, 2021
@nomisRev nomisRev deleted the cu-et6b7a-deprecate-concurrentvar branch February 25, 2021 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants