- walkdir: Add Error docs to methods that return Result
- walkdir: Use
?in docs instead of unwrapping - walkdir: Add example for content_first
- walkdir: Add links to other walkdir items in DirEntry docs
- walkdir: Add links to other walkdir items in Iter and IterFilterEntry docs
- walkdir: Add links to other walkdir items in WalkDir docs
- walkdir: Add links to other walkdir items in WalkDirIterator docs
- walkdir: Document that
IterandIterFilterEntryare the result of trait methods - walkdir: Correct errors in WalkDir type docs
- walkdir: Add html_root_url attribute
- walkdir: Implement Debug for WalkDir, Iter and IterFilterEntry
- walkdir: Add build badges to Cargo.toml
- walkdir: Add categories to Cargo.toml
- walkdir: Rename Iter to IntoIter
- walkdir: Rename IterFilterEntry to FilterEntry
- walkdir: Link references to std in docs
- walkdir: Make skip_current_dir and filter_entry inherent methods
- walkdir: Make WalkDir Send + Sync
- walkdir: Document why unwraps won’t fail
- walkdir: Remove re-export of is_same_file
- walkdir: Change OsString args in sort_by to OsStr
- walkdir: Move DirEntry::ino method to an extension trait
- cookbook: Use
filter_entryin walkdir example - cookbook: “decompress a tarball while removing a prefix from the paths”
- cookbook: Move to skeptic 0.10
Right now, bindgen generates unstable Rust code by default. That’s the wrong choice for a default, it should generate stable Rust code by default.
Who wants to fix this easy, good-first-bug?
Another default that should change is the way we translate C/C++ enums to Rust:
Right now, bindgen computes some properties of the C/C++ items it is generating bindings for in an ad-hoc way. Example properties we’re computing include whether a struct can derive Debug or if it has a vtable. The ad-hoc approach has proven to be error prone (and I suspect inefficient as well). We now have infrastructure to do these analyses in a more principled way and we’re looking for some help porting them 
Meta issue (has context + discussion): https://github.com/servo/rust-bindgen/issues/536
Issues for porting each computation:
-
has_vtable: https://github.com/servo/rust-bindgen/issues/765 -
can_derive_copy: https://github.com/servo/rust-bindgen/issues/766 -
can_derive_debug: https://github.com/servo/rust-bindgen/issues/767 -
is_unsized: https://github.com/servo/rust-bindgen/issues/768
Cheers 
We’ve recently released PumpkinDB 0.2 and there are a lot of upcoming major improvements; and we’re always looking for contributors interested in this topic. We also maintain a list of “starter” issues, some of which you can find below:
https://github.com/PumpkinDB/PumpkinDB/issues/294
Cheers!
1 Like
https://github.com/brson/rust-api-guidelines/issues/52
https://github.com/brson/rust-api-guidelines/issues/55
Rust is in great need of volunteers interested in making a dent in some of the libz blitz crates. There are a bunch of important crates that need to be polished up (like csv, mime, regex, semver, tar, threadpool, toml), but the first step for each is figuring out the the polish to be applied. This task basically amounts to comparing these API guidelines to a given crate, noting where the crate can be improved, and posting to an internals thread for feedback, then finally filing issues and posting them back here to solicit help resolving them.
Imagine the impact you can have by generating and resolving 20 issues against the toml crate!
There are more details about the process in this post. If you are interested but the process looks intimidating, feel free to email me and I can help you get started.
Sorry this doesn’t fit into a one-liner for twir, but I know plenty of people ‘front-run’ this thread, so maybe somebody will see and be interested.
Some cookbook recipes in need of writing:
Also still soliciting recipe ideas for regex, ring, csv, glob, same-file.
We need help evaluating three crates right now. Details explained on thread.