I should note that that issue probably requires a lot of digging/learning because I don't know anything really.
Now that ring has ECDSA signing, it would be nice to add it jsonwebtoken: https://github.com/Keats/jsonwebtoken/issues/21
This should be fairly straightforward and self-contained to the
A little issue to get one's feet wet:
The language-rust project (Rust syntax highlighting) could need some assistance.
It's an npm / Atom package I started from scratch several years ago and quite widely used (Atom, VSCode, GitHub, many others). I think it's generally in good shape. There are some minor bugs (e.g. with nested generic parameters) and some missing features (e.g. no async/await syntax support yet), but nothing really bad. Unfortunately, I'm not a JS expert and especially with more special cases I'm lacking time and JS or npm (or Atom) knowledge for having answers to every issue.
Also, Rust is gaining popularity and so more people come to discuss things. Often people come from other languages or IDEs and sometimes complain about the editor switching to recommended settings (4 spaces, 99 chars), or not having enough snippets. I feel like some presence of the Rust community there would be nice so that there are more balanced opinions on these topics. Some help with PR reviews (most people sadly submit PRs without tests) would be nice too.
The intl_pluralrules crate is seeking review.
intl_pluralrules is a low level API which enables many higher level internationalization and localization APIs. You can read more about it in the introduction blog post.
Since the library will be used in many performance-critical places (first paint path for multilingual software) and we have full control over how we generate and store the plural rules, we'd like to focus on maximizing the performance and minimizing the memory footprint of the library.
For that we're seeking advice and review from members of the community experienced in the topic.
auto_impl has a few issues for beginners interested in working with the new proc macro API. With the crate
auto_impl, you can easily implement your trait for certain "wrapper types" (e.g.
&T where T: YourTrait).
We'd love to get more people involved! I'd be glad to mentor anyone interested in helping out.
Link to issue tracker with
E-easy filter. I'm not sure if it's preferred to post single issue on TWiR. In that case, here are the four links:
- Emit warning on empty proxy type list: https://github.com/auto-impl-rs/auto_impl/issues/24
FnMut: cannot borrow immutable argument: https://github.com/auto-impl-rs/auto_impl/issues/23
- Explicitly pass type parameters when delegating the method: https://github.com/auto-impl-rs/auto_impl/issues/19
- Add super trait bound to proxy type: https://github.com/auto-impl-rs/auto_impl/issues/18
I also posted this on Reddit.
I might as well take advantage of this call for participation stuff, so...
Crater now has a contributing guide and a few issues with mentoring instructions!
Quinn has some good first issues, listed here:
I'm looking for someone to update the parser in macro_railroad, the syntax-diagram generator for
syn-0.15 (from 0.14). There are some bugs in the current parser which we also never got around to fixing. Tracking issue is here.
The imag project is looking for contributors:
Feel free to PM me here, mail via the mailinglist or send a direct mail if you have any questions!
Hiya, I'd like some help on implementing serialization of enums using the externally tagged representation for the TOML crate.
I've done all I can do get Ruby & Rust integrated and working on the Windows OS with Rutie and I need your help to get an issue resolved.
macro_railroad is looking for a contributor in the underlying syntax-diagram library: Most macros' syntax runs wide horizontally, making the resulting diagram hard to read on small screens. We can easily mitigate this in the underlying presentation layer by overflowing long-running
Stacks. The required primitives are basically already in place.
Tracking issue here
I've implemented basical parts like parsing and code generation. But it requires much more work.
For demonstration, it works like
I'm planning to start the work on Tera 1.0 but time is limited.
The main thing I would like help with is converting error handling from
error-chain to standard
Error: Consider remove error_chain dependency · Issue #297 · Keats/tera · GitHub