msrd0

Results 68 issues of msrd0

The `Default` implementation for some of your options structs like `CreateExecOptions` or `ListContainerOptions` require the type parameter `T` to also implement `Default`, eventhough this is not necessary because it is...

How can I use this crate when using syn and proc-macro2 for parsing my input? [`proc_macro2::Span`](https://docs.rs/proc-macro2/latest/proc_macro2/struct.Span.html) gives me a start and end [`proc_macro2::LineColumn`](https://docs.rs/proc-macro2/latest/proc_macro2/struct.LineColumn.html), not an offset as this crate expects....

As of right now, the `IntoResponse` for `Result` just calls the `IntoResponse` implementation for either type. This is fine in most use cases, but is counter-intuitive when `Err("API Error")` generates...

discussion
refactor
breaking-change

Gotham's `to_file` and `to_dir` methods internally handle compression and parsing the `Accept-Encoding` header. However, these methods cannot be used all the time, so it would be nice if we export...

non-breaking-change

Currently, all handler functions take either `State` or `&State` as their only parameter, and need to retrieve all information they need in user code. It would be more convenient if...

proposal
discussion

Consider the following code (using `AsChangeset` instead / in addition to `Insertable` produces the same error message): ```rust #[derive(Insertable)] struct Foo { #[column_name = "type"] ty: String } ``` This...

bug
enhancement
good first issue

Debian bullseye has been released last month and is the current stable branch: https://www.debian.org/News/2021/20210814 I just tried to update but I received the following error message: ``` Ign:4 http://pkg.mxe.cc/repos/apt bullseye...

This pull request introduces a `HelpMessage` trait that is implemented for every struct that derives `FromArgs`, allowing the user to manually display the help message generated by `argh`. Also, the...

Using `/*! */` and `//! ` is basically just syntactic sugar for a `#![doc = r#""#]` attribute. However, cargo-readme does not currently parse those attributes, and generates an empty readme...