# Use synchronous locks for \`Peer\` state · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/9e4b118214e2e72f271fcf5c6836435cfad3d54c)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 9e4b118214e2e72f271fcf5c6836435cfad3d54c

Requested commit: 9e4b118214e2e72f271fcf5c6836435cfad3d54c

Commit: 9e4b118214e2e72f271fcf5c6836435cfad3d54c

Tree: 0dab9c26abd241c90159e415cf0ee0bc197e9da4

Author: Antonio Scandurra

Committer: Antonio Scandurra

## Message

```
Use synchronous locks for `Peer` state

We hold these locks for a short amount of time anyway, and using an
async lock could cause parallel sends to happen in an order different
than the order in which `send`/`request` was called.

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

```

## Parents

- [310def292340933b5a462fcd99d9e77cfddb899d](https://git.cafe/gitcafe/zed/commit/310def292340933b5a462fcd99d9e77cfddb899d?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/9e4b118214e2e72f271fcf5c6836435cfad3d54c?format=markdown)