The libz blitz is in need of someone to lead the walkdir evaluation.
1 Like
If anyone has some free time:
1 Like
1 Like
https://github.com/rust-lang/rust/issues/42349
https://github.com/rust-lang-nursery/rustup.rs/issues/1144
1 Like
From the libz blitz:
- log: Support construction of
LogRecords andLogMetadata - log: Expand log! docs for
max_level_* - log: Maintaner wanted for env_logger
- reqwest: Expose RedirectAttempt and RedirectAction types
- reqwest: Add realistic examples for Response
- reqwest: Document Body constructors
- reqwest: Document Error
- reqwest: Add examples for
body - url: Document percent_encoding module
- url: Implement Debug for many types
- url: Put error conditions in “Errors” sections
- url: Explain the term “fragment”
1 Like
From my project to port Haskell’s C parser and Corrode to Rust, I have this [medium] sized task available: https://github.com/tcr/corrode-but-in-rust/issues/65
I’m happy to mentor people through this task. The translation project is entirely in Rust (no Haskell knowledge necessary).
2 Likes
https://github.com/brson/stdx/issues/15
https://github.com/brson/stdx/issues/32
https://github.com/brson/stdx/issues/33
https://github.com/brson/stdx/issues/34
https://github.com/brson/stdx/issues/35
https://github.com/brson/stdx/issues/36
1 Like
https://github.com/rust-lang/rust/issues/42349
https://github.com/rust-lang-nursery/rustup.rs/issues/1144
1 Like
Perceptia is dynamic window manager with support for Wayland. It is young so I guess it is the most exiting time to become a contributor. Here are couple of example issues suitable for new-commers (many more interesting ones wait on github):
Offscreen mode with VNC or Spice would be nice feature to have. Is someone working in support for these protocols in Rust?
I filed a lot of issues in lyon’s repository, a lot of which are labelled “help wanted” and most of them are easy. I’ll be happy to mentor them.
- (easy) Compute the bounding rectangle of line segments and triangles.
- (easy) Provide feedback and help make the code and docs easier to understand and discover.
- (easy) Make sure the code conforms to the rust API guidelines.
- (easy) Add fuzz testing for the fill tessellator
- (easy-ish) Implement tessellating circle strokes.
- (easy-ish) Implement tessellating rounded rectangle strokes.
- (easy-ish) Compute vertex normals in the basic shapes tessellators that don’t already do it.
- (medium) Implement bevel line joins.
- (medium) Implement round line joins.
- (medium) Implement round line caps.
- (medium) Implement miter limits.
- 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 