Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metric atomic usize #1

Closed
wants to merge 1,347 commits into from
Closed

Metric atomic usize #1

wants to merge 1,347 commits into from

Conversation

rcoh
Copy link
Owner

@rcoh rcoh commented May 29, 2024

Motivation

tokio-rs#6556 (comment)

Metrics should not use Loom atomics. This clarifies this in code and also gives the opportunity to make a cleaner interface for metrics. We could potentially use this interface in the future to track things like the maximum value etc.

Solution

Introduce MetricAtomicUsize as the equivalent of MetricAtomicU64

nicflower and others added 30 commits September 19, 2023 16:01
…6038)

Signed-off-by: Muhan Song <songmuhan@stu.pku.edu.cn>
wathenjiang and others added 29 commits May 3, 2024 15:37
Co-authored-by: Akhil Thankachan Thomas <Akhil.Thomas@in.bosch.com>
…6578)

Signed-off-by: hi-rustin <rustin.liu@gmail.com>
The code for `output` indicates that only sets `stdout` and `stderr`, 
yet the docs for `stdin` indicated that it too would be set. This seems 
like it was just a simple copy/paste typo, so correct `stdin` to note
that it just defaults to `inherit`.

Fixes tokio-rs#6577.
nix 0.29.0 and mio-aio 0.9.0 use I/O Safety.

Co-authored-by: Frederick Mayle <fmayle@google.com>
The previous NamedPipeServer doc example seemed to imply that the return
type of `NamedPipeServer::connect()` was a
`Future<Result<some_kind_of_client>>>`, however, `connect()` returns a
`Future<Result<()>>>`. The following line of code reopening the pipe
would shadow the newly connected pipe immediately, making the following
spawned task pointless. Hopefully these changes make it more clear what
should be happening in the example.
@rcoh rcoh closed this May 29, 2024
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.