A curated list of Rust code and resources that do NOT exist yet, but would be beneficial to the Rust community.
An (unofficial) sub-community of the Rust programming language that wants to close gaps you feel in Rust's ecosystem.
There are two major resources provided in this community at time of writing: the NYAR ecosystem list and issues in the NYAR tracker.
This README is a list with a twofold purpose:
You can jump right into editing this file here. See the contributing guide for information on what you can do to help or if you have questions about this list!
NYAR's issue tracker can help you get ecosystem gaps filled when you participate in:
bounty
tag to indicate which issues have bounties associated.cp437
(see this issue).encoding
and encoding-rs
exist, but don't support this currently.cv-rs
as well as automatically generating bindings like opencv-rust
. Neither are very complete.imageproc
based on image
, but in their words, "This is very much a work in progress".hdf5
crate has been released and is now available on crates.io.tokio
and futures
may be interesting components to use when building this.impl Trait
will probably make developing something like this easier to develop and use.pandoc
crate now exists with CLI bindings!A concurrent std::collections::HashMap
-like structure has not been fully developed yet.
concurrent-hashmap
is still missing methods like iter_mut
, entry
, drain
, and clear
from the original HashMap
interface.evmap
is a different design around eventual consistency, and so departs from the normal HashMap
interface.dashmap
is intended to fit this use case exactly.
rust-minix
is a WIP adding support for the Linux platform, which the author introduced with this blog post.The bindings cover most of the exposed API of Godot 3.2, and are being used on a number of projects in development, but we still expect non-trivial breaking changes in the API in the coming releases.
libm
implementation. These are required to get math functions on #![no_std]
platforms
winapi
supports.fe2o3-amqp
implements the AMQP 1.0 protocol for both client side and server/listener side.Registry.pol
files from Windows machinescalamine
, but no serialization libraries seem available for them, let alone for the entire XML formats that the Office/OpenOffice suites themselves support.beancount
data format has no parser or emitter libraries yet.
quirc
crate, which uses C bindingsserialize.c
module.vobject
, but no "high-level interface" exists yet that uses it or an alternative.
vobject
), but a higher-level API is missing.
miri
seems to be a step in the right direction -- it just needs some love!rustdoc
, which wouldnative-windows-gui
at one point claimed to be approaching feature-completion, but is now unmaintained.carboxyl
looks like it may be a good fundamental building block for this.googleapis
and gRPC would be more performant than using JSON web requests to the Google API, as with google-apis-rs
service.google-apis-rs
uses the Google Discovery service to expose the vast majority of Google Services, but they can be difficult to grok for beginners or someone unfamiliar with Google APIs in general.There is yet to be a library that handles all of these:
For more feature and performance comparisons for existing Rust XML crates, see choose-your-xml-rs
.