Skip to content

Making release() and time() async - #170

Merged
lovelydinosaur merged 3 commits into
encode:masterfrom
cdeler:making-release-and-time-async
Aug 26, 2020
Merged

Making release() and time() async#170
lovelydinosaur merged 3 commits into
encode:masterfrom
cdeler:making-release-and-time-async

Conversation

@cdeler

@cdelercdeler commented Aug 25, 2020

Copy link
Copy Markdown
Contributor

In #169 and #168 you can find pretty the same changes:
AsyncBackend::time , AsyncSemaphore::release and AsyncLock::release have been made async.

I extracted these changes into the separated PR to make the changeset be discussed here.

@cdelercdeler mentioned this pull request Aug 25, 2020
@cdelercdeler changed the title Making release and time asyncMaking release() and time() asyncAug 25, 2020

@lovelydinosaurlovelydinosaur left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yup, I think this'll be fairly uncontroversial.

Wouldn't mind a second review over it, but otherwise I'm good with this.

Note to all: We need this because curio has different expectations (for perfectly decent reasons) about which methods should/shouldn't expose an async interface. Given that this async interface can still call into a sync implementation for trio and asyncio, but that the converse would not be true, we're not really losing anything by adopting curio's constraints in our own internal backend API here.

@florimondmancaflorimondmanca left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks good, thank you!

@lovelydinosaur
lovelydinosaur merged commit a43a4fc into encode:masterAug 26, 2020
@cdeler
cdeler deleted the making-release-and-time-async branch August 26, 2020 09:32
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

3 participants

@cdeler@lovelydinosaur@florimondmanca