| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Framed was designed to encapsulate both AsyncRead and AsyncWrite so
that it could wrap two-way connections. It used Fuse to manage the pinned
io object between the FramedWrite and FramedRead structs.
I replaced the Fuse struct by isolating the state used in reading and
writing, and making the code generic over that instead. This means
the FramedImpl struct now has a parameter for the state, and contains
the logic for both directions. The Framed* structs are now simply
wrappers around this type
Hopefully removing the `Pin` handling made things easier to
understand, too.
|
|
Added GitHub style link fragments to the `[Commit Squashing]`
sections of CONTRIBUTING.md
Fixes: #2506
|
|
* Document common cargo commands
* Add loom command
|
|
|
|
|
|
Edited the last sentence of the first section to improve clarity
|
|
## Motivation
Currently, the process for releasing a new version of a Tokio crate is
somewhat complex, and is not well-documented. To make it easier for
contributors to release minor versions more frequently, there should be
documentation describing this process.
## Solution
This branch adds a section to `CONTRIBUTING.md` describing how to
release a new version of a Tokio crate. The steps are based on those
described by @carllerche in an offline conversation.
I've also added a quick shell script to actually publish new crate
versions. This should make it harder to make mistakes when
publishing.
Signed-off-by: Eliza Weisman <eliza@buoyant.io>
|
|
|
|
Just move a dot to the right place.
|
|
|
|
|
|
|
|
This guide was adopted from the node.js project.
|
