Lines Matching refs:with

7 matter if you are just getting started with Rust or are the most weathered
15 You may also get help with contributing in the `dev` channel, please join
68 be presented with a [basic template][template] that should be filled in. If you
101 explain why you feel that way with additional supporting context, and be willing
109 and triaging issues, but carries with it a necessary review and approval
146 use the API. Documentation tests are run with `cargo test --doc`. This ensures
157 /// // with `use tokio::prelude::*`
169 ///     // do something with `item`
175 /// // Wrap the future with a `Timeout` set to expire in 10 milliseconds.
185 Lines that start with `/// #` are removed when the documentation is generated.
203 /// // Wrap the future with a `Timeout` set to expire in 10 milliseconds.
241   * be entirely in lowercase with the exception of proper nouns, acronyms, and
243   * be prefixed with the name of the crate being changed (without the
244     `tonic` prefix) and start with an imperative verb.
283 From within GitHub, opening a new Pull Request will present you with a
324 to working with the contributor to make the Pull Request better.
370 with the appropriate reason to keep the conversation flow concise and relevant.
377 just not want to have anything to do with `tonic` ever again. The goal is
383 check with the contributor to see if they intend to continue the work before
405    easy to release and figure out what sub crates you need that will work with