Lines Matching +full:test +full:- +full:msrv

6 [![Crates.io][crates-badge]][crates-url]
7 [![Documentation][docs-badge]][docs-url]
8 [![Documentation (master)][docs-master-badge]][docs-master-url]
9 [![MIT licensed][mit-badge]][mit-url]
10 [![Build Status][actions-badge]][actions-url]
11 [![Discord chat][discord-badge]][discord-url]
13 [crates-badge]: https://img.shields.io/crates/v/tower.svg
14 [crates-url]: https://crates.io/crates/tower
15 [docs-badge]: https://docs.rs/tower/badge.svg
16 [docs-url]: https://docs.rs/tower
17 [docs-master-badge]: https://img.shields.io/badge/docs-master-blue
18 [docs-master-url]: https://tower-rs.github.io/tower/tower
19 [mit-badge]: https://img.shields.io/badge/license-MIT-blue.svg
20 [mit-url]: LICENSE
21 [actions-badge]: https://github.com/tower-rs/tower/workflows/CI/badge.svg
22 [actions-url]:https://github.com/tower-rs/tower/actions?query=workflow%3ACI
23 [discord-badge]: https://img.shields.io/discord/500028886025895936?logo=discord&label=discord&logoC…
24 [discord-url]: https://discord.gg/EeF3cQw
39 implementing these components in a protocol-agnostic, composable way. Typically,
54 * [`tower-service`]
55 * [`tower-layer`]
56 * [`tower-test`]
61 crates, [`tower-service`] and [`tower-layer`]. This crate contains
62 re-exports of those core traits, implementations of commonly-used
64 Finally, the [`tower-test`] crate provides tools for testing programs using
85   servers in a reusable manner. This might be general-purpose middleware
87   other Tower users!) or application-specific behavior that needs to be
90   protocols (such as HTTP) can depend on `tower-service` to use the
94   Similarly, a server might be created from a user-provided [`Service`].
102 A number of third-party libraries support Tower and the [`Service`] trait.
105 * [`hyper`]: A fast and correct low-level HTTP implementation.
106 * [`tonic`]: A [gRPC-over-HTTP/2][grpc] implementation built on top of
107   [`hyper`]. See [here][tonic-examples] for examples of using [`tonic`] with
110   [here][warp-service] for details on using [`warp`] with Tower.
111 * [`tower-lsp`] and its fork, [`lspower`]: implementations of the [Language
114   makes use of the Tower ecosystem: [`tower`], [`tower-http`], and
115   [`tower-test`]. See [here][kube-example-minimal] and
116   [here][kube-example-trace] for examples of using [`kube`] with Tower.
120 [tonic-examples]: https://github.com/hyperium/tonic/tree/master/examples/src/tower
123 [warp-service]: https://docs.rs/warp/0.2.5/warp/fn.service.html
124 [`tower-lsp`]: https://crates.io/crates/tower-lsp
126 [lsp]: https://microsoft.github.io/language-server-protocol/
129 [kube-example-minimal]: https://github.com/clux/kube-rs/blob/master/examples/custom_client.rs
130 [kube-example-trace]: https://github.com/clux/kube-rs/blob/master/examples/custom_client_trace.rs
131 [`tower-http`]: https://crates.io/crates/tower-http
169 [`tower-service`]: https://crates.io/crates/tower-service
170 [`tower-layer`]: https://crates.io/crates/tower-layer
171 [`tower-test`]: https://crates.io/crates/tower-test
173 [open a PR]: https://github.com/tower-rs/tower/compare
178 Tower will keep a rolling MSRV (minimum supported Rust version) policy of **at
179 least** 6 months. When increasing the MSRV, the new Rust version must have been
180 released at least six months ago. The current MSRV is 1.49.0.