yaahc

Keybase proof

I hereby claim:

• I am jrlusby on github.
• I am yaah (https://keybase.io/yaah) on keybase.
• I have a public key ASClIOUdq1vNm7CUafVI82T9GOkqiMjYLxJodV5odBzmPgo

To claim this, I am signing this object:

yaahc

master ✗ $ cargo clippy
    Checking clippytest v0.1.0 (/home/jlusby/git/rust/clippytest)
error: this `if` has identical blocks
 --> src/main.rs:3:12
  |
3 |       } else {
  |  ____________^
4 | |     }
  | |_____^
  |

yaahc

[2019-03-15T04:08:59Z DEBUG cargo] exit_with_error; err=CliError { error: Some(ProcessError { desc: "process didn\'t exit successfully: `clippy-driver rustc --edition=2018 --crate-name clippytest src/main.rs --color always --crate-type bin --emit=dep-info,metadata -C debuginfo=2 -C metadata=f7a52620a1cf4b3b -C extra-filename=-f7a52620a1cf4b3b --out-dir /home/jlusby/git/rust/clippytest/target/debug/deps -C incremental=/home/jlusby/git/rust/clippytest/target/debug/incremental -L dependency=/home/jlusby/git/rust/clippytest/target/debug/deps` (exit code: 1)", exit: Some(ExitStatus(ExitStatus(256))), output: None }

yaahc

diff --git a/tokio-trace-env-logger/examples/hyper-echo.rs b/tokio-trace-env-logger/examples/hyper-echo.rs
index db8bd1b..4d753a0 100644
--- a/tokio-trace-env-logger/examples/hyper-echo.rs
+++ b/tokio-trace-env-logger/examples/hyper-echo.rs
@@ -124,7 +124,7 @@ fn main() {
 
     tokio_trace::subscriber::with_default(subscriber, || {
         let addr: ::std::net::SocketAddr = ([127, 0, 0, 1], 3000).into();
-        let mut server_span = span!(Level::TRACE, "server", local = &field::debug(addr));
+        let server_span = span!(Level::TRACE, "server", local = &field::debug(addr));

yaahc

layout	title	categories
post	Lifetime definitions	rust rustlang lifetime borrow reference generics

Confusing terms

My problem with understanding lifetime heavy code is that I find all the terms involved confusable. This post is my attempt to record clear distinctions

yaahc

//! Struct for merging multiple sorted channels into a single iterator

use crossbeam::channel::Receiver;
use std::cmp::Ordering;
use std::fmt::Debug;
use tracing_proc_macros::trace as instrument;

/// Representation of a merged set of channels as an iterator
///
/// Depends upon the assumption that all data in chans is already sorted.

yaahc

Insert catchy title for the contribution tour

Abstract

The story so far of my experience joining the rust FOSS community. Starting from learning about the community and its values, through my initial efforts to contribute to various projects, and finishing in my current more refined views towards selecting open source work and how to approach it constructively.

Details

yaahc

# Rustaceans! We Can Help!

## Abstract

Are you a new rustacean trying to take your first steps into rust's open source
community? Are you trying to meet people in the rust community but don't know
where to start? Are you a maintainer interested in attracting new contributors?
Then have I got the talk for you! Together we will explore some approaches to
finding issues to work on, finding new projects, structuring your projects to
help new contributors, and meeting other rust developers to become a happy and

yaahc

https://twitter.com/search?q=rustc%20OR%20rustlang%20OR%20url%3Acrates.io%20OR%20url%3Aplay.rust-lang.org%20OR%20(rust%20conference%20OR%20rust%20gay%20OR%20rust%20client%20OR%20rust%20server%20OR%20rust%20wasm%20OR%20rust%20web%20OR%20rust%20assembly%20OR%20rust%20perf%20OR%20rust%20app%20OR%20rust%20syntax%20OR%20rust%20safety%20OR%20rust%20github%20OR%20rust%20http%20OR%20rust%20compiler%20OR%20rust%20program%20OR%20rust%20code%20OR%20rust%20software%20OR%20rust%20url%3Agithub.com%20OR%20rust%20async)%20-belt%20-colour%20-url%3Atwitch&src=typed_query&f=live

Alternatively if you follow a lot of rust people

https://twitter.com/search?q=rust&src=typed_query&f=live&pf=on

yaahc

PR Ideas

moved to https://github.com/yaahc/yaahc/issues/1