Repository files navigation

An (unofficial) sub-community of theRust 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 andissues in the NYAR tracker.

This README is a list with a twofold purpose:

• Enumeratespecific use cases and their problems domains that do not yet have a robust ecosystem in Rust.
  • The definition of "specific" and "robust" for this list is yet to be determined!
• Encourage the Rust community to approach gaps in the Rust ecosystem by providing this list as a point of collaboration!

You can jump right into editing this filehere. See thecontributing 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:

• Voting on your favorite issues to let people know you'd use something, optionallycommenting and explaining your use case.
• Placing bounties on issues you're particularly passionate about, since issues are where BountySource integrates! We use thebounty tag to indicate which issues have bounties associated.

• Documentation
  • Stack Overflow
• Libraries
  • Character encodings
  • Computer Vision
  • Data processing
  • Data structures
  • Dynamic programming analysis
  • Embedded development
  • Game development
  • Geometry
  • Geospatial Information Systems
  • Machine Learning
  • Mathematics
  • Native desktop application integrations
    • Microsoft Office
  • Parsers/Emitters
  • Personal information management
  • Rust Toolchain
  • User Interfaces
  • Web bindings
    • Google API
  • XML

• There are many older Rust questions on Stack Overflow that wouldn't work with today's Rust because of syntax that has changed since the release of 1.0, or that may have better solutions because of other Rust ecosystem developments.
  • See#4 for an SO query and a list of these known issues!

• Full support forcp437 (seethis issue). Implementedhere!
  • More fully-featured encode/decode libraries likeencoding andencoding-rs exist, but don't support this currently.
  • Adecode-only library exists, the development of which seems to have stopped.

• Some work has been done to create OpenCV bindings incv-rs as well as automatically generating bindings likeopencv-rust. Neither are very complete.
• Piston hasimageproc based onimage, but in their words, "This is very much a work in progress".

• DDS librarywikijhelovuo/RustDDS ands2e-systems/dust-dds now exist!
• HDF5 (see alsoWikipedia andthis Reddit post) A stable version ofhdf5 crate has been released and is nowavailable on crates.io.
• A good stream processing pipeline with back pressure doesn't yet exist for an asynchronous data processing pipeline
  • RxRust is an older attempt to implement this according to thereactive streams model -- it currently seems closest to this use case.
  • tokio andfutures may be interesting components to use when building this.
  • New features soon to come in Rust likeimpl Trait will probably make developing something like this easier to develop and use.
• Bindings forpandoc Apandoc crate now exists with CLI bindings!
• Bindings forgit-annex

• A concurrentstd::collections::HashMap-like structure has not been fully developed yet.

  • concurrent-hashmap is still missing methods likeiter_mut,entry,drain, andclear from the originalHashMap interface.
  • evmap is a different design around eventual consistency, and so departs from the normalHashMap interface.

  dashmap is intended to fit this use case exactly.

• Binary instrumentation tools likeIntel Pin orDynamoRIO are useful for embedded applications. An ecosystem around them (which doesn't exist yet!) could include:
  • Bindings to the C APIs associated with existing applications (for instance,Intel Pin andDynamioRIO)
  • Libraries or applications implementing the features of the aforementioned in Rust

• MINIX support isnonexistent! still a WIP.
  • rust-minix is a WIP adding support for the Linux platform, which the author introduced withthis blog post.

• Integration with existing mature game engines is poor at time of writing.
  • Unreal Engine has hadsome prior work accessible by making an Unreal account, but nothing has been made freely public at time of writing.
  • Unity3D currently has no published crates for Rust interop.
  • Godot Engine allows Rust interop viagodot-rust. Authors'note on stability:

    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.

• No mature game engine written in pure Rust exists yet.
  • Part of a mature solution will need to include a rich and robust editor. Examples can include:
    • Unreal Editor
    • Unity Editor
  • Amethyst is active andhas a roadmap for becoming production-ready. Halted development.
  • Bevy is a new project built with the learnings of the Amethyst project. See theroadmap here.
  • Fyrox is a 3D + 2D game engine which includes afull graphical editor, and an example3D FPS game built using it.

• PCL equivalent - point clouds, essential 3D geometry functions
• Voxel library, operations and representation of voxel data. There isa piston crate for rendering voxels but this isn't suitable for working on domains like medical data, more geared towards game development. To enable processing in scientific domains like medicine there needs to be processing functions such as being able to: convert to triangular mesh, thresholding, and morphology. This is because things like MRI data is expressed as voxels, thresholding can separate grey and white matter in the brain, morphology identifies shapes and structures inside the body etc.

• OGC standards - multiple crates for standards for encoding, sharing or manipulating geospatial datalink. There's already a crate forGeoJSON but none of the others appear to have crates.
• More complete GDAL wrapper (or pure rust alternative).rust-gdal is an incomplete wrapper so needs work.

• Machine learning toolkit like scikit-learn in Python (both rust-learn and rusty-machine are insufficient). Rust-learn only supports classification, rusty-machines misses support for sparse data and serialization. Both of them miss quite common unsupervised techniques (like PCA).
• Deep learning toolkit with GPU support a good flexibility (think Tensorflow or Chainer in Python). Most of the current libraries are either simplistic (you cannot do seq2seq network in them for example), or miss GPU support.

• Sparse matrix libraries (SPRS library needs some love, the basics are there but advanced linear algebra is missing)
• Designing low latency DSP algorithms suitable for embedded use (common filters, analysis functions)
• Library for nonlinear dynamical or chaotic systems (solvers, numeric methods etc.)
• A pure Rustlibm implementation. These are required to get math functions on#![no_std] platforms
  • Them crate has made some headway here, though it hasn't been maintained recently.
  • Thelibm crate is a port oflibm functionality from musl and newlib to Rust, with the aim of eventually being merged intocore.

• An interactive Visual Basic uses for scripting by using the COM interface, which I believewinapi supports.

• AMQP 1.0 - While there are several libraries for AMQP 0.9.1, the AMQP 1.0 spec represents a significant departure from the previous version.fe2o3-amqp implements the AMQP 1.0 protocol for both client side and server/listener side.

• Ability to parseRegistry.pol files from Windows machines -- implementedby this person!
• Common office document formats are yet to have more mature solutions:
  • Excel/Calc spreadsheet deserialization seems available withcalamine, butno serialization libraries seem available for them, let alone for the entire XML formats that the Office/OpenOffice suites themselves support.
  • Otherwise, OpenOffice and Microsoft Office
• There is currently no library to convert between different office document formats.
• Thebeancount data format has no parser or emitter libraries yet.
  • A builder interface for a higher-level emission API would also be nice.
  • Bindings to thePython implementation of beancount do not yet exist.
  • Animplementation of Beancount bindings, parser, and emitter in Rust is currently WIP, and contributors have been requested.
• There is no pure-Rust solution for QR decoding. The only other crate that handles QR decoding is thequirc crate, which uses C bindings -- implementedby @Wanzenbug andby @piderman, the latter of which was announced onReddit. Seethe PR.
• TheRData file format does not have a parser or emitter yet.
  • Currently, this formatted is implemented for the R language in theserialize.c module.
• There are no SGML parsers or emitters on crates.io at all.
  • This is mostly a legacy markup language used for legacy type setting and supported in applications likeAPP (AKA 3B2).

• Contacts viavCard have been implemented usingvobject, but no "high-level interface" exists yet that uses it or an alternative.
• iCalendar parsing has been implemented via several crates (i.e.,vobject), but a higher-level API is missing.

• Astable Rust interpreter does not yet exist, which would made code exploration easier.
  • miri seems to be a step in the right direction -- it just needs some love!
• No debugging experience offers integration withrustdoc, which would
• A rustdoc backend for generatingzeal/dash docsets is missing.

• A mature framework for Windows native UI has yet to be established.
  • native-windows-gui at one point claimed to be approaching feature-completion, but is now unmaintained.
• Abstractions over native UIs for each platform have yet to be available in pure Rust.
• A good reactive UI library complete with event-driven state management comparable toRedux does not yet exist.
  • carboxyl looks like it may be a good fundamental building block for this.

• Generation of Google bindings usinggoogleapis and gRPC would be more performant than using JSON web requests to the Google API, as withgoogle-apis-rs service.
• There is room for more idiomatic APIs for Google in general.google-apis-rs uses theGoogle 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:

• General purpose DOM tree
• Proper encoding handling
• DTD handling
  • including the disabling of features with security implications like entity expansion bombs
• XML Schema validation
• XPath
• XQuery
• XSLT 1.0/2.0/3.0
• Option to preserve input style
• Isfast

For more feature and performance comparisons for existing Rust XML crates, seechoose-your-xml-rs.