lambda_http fails to compile with default-features = false #697
Description
If you depend on lambda_http 0.8.1 with default features set to false, then the following compile errors occur:
Checking lambda_http v0.8.1
error[E0004]: non-exhaustive patterns: type `&LambdaRequest` is non-empty
--> ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lambda_http-0.8.1/src/request.rs:54:15
|
54 | match self {
| ^^^^
|
note: `LambdaRequest` defined here
--> ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lambda_http-0.8.1/src/request.rs:38:10
|
38 | pub enum LambdaRequest {
| ^^^^^^^^^^^^^
= note: the matched value is of type `&LambdaRequest`
= note: references are always considered inhabited
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern as shown
|
54 ~ match self {
55 + _ => todo!(),
56 + }
|
error[E0004]: non-exhaustive patterns: type `&RequestOrigin` is non-empty
--> ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lambda_http-0.8.1/src/response.rs:64:15
|
64 | match request_origin {
| ^^^^^^^^^^^^^^
|
note: `RequestOrigin` defined here
--> ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lambda_http-0.8.1/src/request.rs:73:10
|
73 | pub enum RequestOrigin {
| ^^^^^^^^^^^^^
= note: the matched value is of type `&RequestOrigin`
= note: references are always considered inhabited
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern as shown
|
64 ~ match request_origin {
65 + _ => todo!(),
66 + }
|
For more information about this error, try `rustc --explain E0004`.