[TWiR] Call for Participation

I have something a bit different, I don’t know if it fits here.

I asked a question on StackOverflow: What are the similarities and differences between C++'s concepts and Rust’s traits? I know a lot of people that are really interested in an answer to it. @matthieum already attempted to answer it (which I am very happy about), but they mention that they have not yet worked with concepts " so take this answer with a grain of salt.".

It would be cool to maybe find someone who really knows C++ concepts to answer this question. So I thought that we can maybe add this to TWiR to reach a wider audience? Something like:

Do you know a lot about C++ concepts? Please consider answering this question or improving existing answers (e.g. by pointing out flaws): What are the similarities and differences between C++'s concepts and Rust’s traits?

I will also add a bounty to the question in a few days (before the next TWiR is released).

eazy and tedious, requires building large projects.

This is waiting on someone with a fairly powerful and idle computer doing a comparison of time cargo generate-lockfile with a build of master vers a build with this PR on some large project like servo or like rustc.

Hi, I include a renaming issue:

Solving this issue should require basic familiarity with Rust, no additional knowledge about the Offst project is required.

This linear algebra library needs more tests, easy issue if you know linear algebra.
You can see what the functions are supposed to do from netlib.

1 Like


We could use a more experienced embedded developer to help us with a problem in the Rubble BLE stack.

Blog post explaining the issue:

Issue itself:

1 Like


I could use some help with the ConTrie crate. I’ve created two tickets for some of the work that needs to be done, both is writing code that is similar to some other code already in the crate so it should be quite beginner friendly.

1 Like


I’m the Windows maintainer of Winit. We could use some help getting stuff done on… well, all platforms, really, but especially macOS, X11, Android, and iOS.


I have two simple and self-contained issues for new Rustaceans in my new crate js_int:

There’s another one that might be harder, but probably is relatively easy too:

1 Like

Here are some simple rustc-guide documentation issues that would be really good candidates for first PR's to rust:

1 Like

Notify: looking for maintainers

I have one good first issue for next weeks TWIR :slight_smile: I will try to find more in the next few days.

1 Like
1 Like

For Hacktoberfest I'd like to get my crate rustfm-scrobble to v1.0.

I've been working on it for a few years, it's a very simple little crate - a small API client for Last.fm's Scrobble API. There are a few issues left before a 1.0 release, all of them on GitHub with the 'Hacktoberfest' label.

Good opportunity to get some Hacktoberfest PRs and work on improving the Rust ecosystem.

Tokamak and Bastion looking for maintainers!
For Tokamak project:

For Bastion project:

My static_assertions crate is now 1.0! :slight_smile:

I wrote about it at https://nikolaivazquez.com/posts/programming/rust-static-assertions-1_0/

1 Like

Embark has been busy tagging our PRs for Hacktoberfest - lots of areas where we want help and we'll add more throughout the month!
http://bit.ly/embarkhacktober (logged in)
http://bit.ly/embarkhacktober1 (not logged in)

1 Like

For async-std we have a few issues this week we could use help with!

1 Like

For async-std we have another set of issues this week we could use help with!

There are also a lot of Stream combinators that are waiting to be implemented: https://github.com/async-rs/async-std/issues/129

These should all be a fun challenge to solve, but not too hard that it's no longer fun. We already have a lot of time-related code in async-std that can be referenced for implementing these.

1 Like