request-for-implementation
request-for-implementation copied to clipboard
dtolnay
Crates that don't exist, but should
In https://github.com/dtolnay/serde-yaml/issues/94 I would like to move serde-yaml off of [yaml-rust](https://github.com/chyh1990/yaml-rust) as a YAML backend and to a much simpler backend with support for a minimum viable subset of YAML...
I would like to be able to write: ```rust dtd!("path/to/note.dtd"); ``` or possibly inline: ```rust dtd! { } ``` and have this expand to the right data structures to represent...
Like all of the standard library's traits, Serde's traits are limited to fixed size arrays up to an arbitrary maximum size. Serde defines Serialize and Deserialize impls for arrays up...
Std path does some weird things with UNC paths (`\\?\`). For one [std::fs::canonicalize](https://doc.rust-lang.org/std/fs/fn.canonicalize.html) always returns one whether it is needed or not. Then `path.join` will just do a string concatenation...
`winapi_util` and `winapi_easy` cover small portions of it, but we have yet to see a fully covered set of bindings à la [Nix](https://crates.io/crates/nix). It should wrap raw handles in more...
A marker to allow compile-type checks for when the uniquely serializable representation in required
Sometimes you want to build a data structure that, when serialized, in guaranteed to have the same representation for the same data. An example of this would be a [BitTorrent...
Assume we have ```rust struct S{ a: u32 } struct T { s: S, t: [u32; 5] } fn foo(x: bool) -> u32 { ... } ``` and `let mut...
Originally filed as https://github.com/serde-rs/json/issues/318, but since this will involve quite a bit more unsafe code than currently exists in serde_json I think it could be better to put in a...
In the GitBook that backs https://serde.rs, I use [several GitBook plugins](https://github.com/serde-rs/serde-rs.github.io/blob/67d32d8af27e27f367438e25dc90dde6be10a660/book.json#L5), a few of which I wrote myself. For example I have a plugin that lets me insert playground links...
Just like #2, but for XSDs. Can be useful in generating building blocks for crates handling OOXML or other complex xml formats.