rust-unofficial/awesome-rust

A curated list of Rust code and resources.

awesome-rust's Issues

add kylyp project.

kylyp: The project use rust, rocket, diesel, postgresql, and responsive design to build a new Forum.
kylyp

Add array_tool to Data Structures

Crate named array_tool. Helper methods for Vector collections.

Add FTP client

https://github.com/mattnenterprise/rust-ftp

Change format for list entries

As awesome-rust grows, there are a few tweaks that may improve readability, consistency, and load times. Before making changes en masse, it would be great to hear anyone's thoughts and a green light from maintainers.

• e.g current format (for half the current list. currently, not all entries include links to crates)
  • kbknapp/clap-rs [clap] — a simple to use, full featured command-line argument parser
  • docopt/docopt.rs [docopt] — a Rust implementation of DocOpt
  • TeXitoi/structopt [structopt] — parse command line argument by defining a struct
  • killercup/quicli [quicli] — quickly build cool CLI apps in Rust
• proposed changes
  • present the name of the project/library first, which brings it closer to the name used in a cargo.toml in many cases. keep it linked to the repository.
  • remove build passing icon. the page makes many requests to travis for badge SVGs. especially from a slower connection, the loading of the badges move the page as they affect the vertical spacing of the lists. if a user jumps or scrolls to the bottom of the page upon opening, they may need to wait before the page stays still. this change loses a nice splash of color the list, but reduces load times and prevents the unaligned badges slowing and littering the page.
  • move crates links a sub-list. this gives the description breathing room and allows us to include additional information/links on the sub-list, e.g. a direct link to the docs.
• proposed format
  • clap — a simple to use, full featured command-line argument parser.
    • crates.io - docs
  • docopt — a Rust implementation of DocOpt.
    • crates.io - docs
  • structopt — parse command line argument by defining a struct.
    • crates.io - docs
  • quicli — quickly build cool CLI apps in Rust.
    • crates.io - docs
• a simpler alternative
  • clap — a simple to use, full featured command-line argument parser.
  • docopt — a Rust implementation of DocOpt.
  • structopt — parse command line argument by defining a struct.
  • quicli — quickly build cool CLI apps in Rust.

Industrial automation category?

I'd like to add the tokio-modbus library but I'm missing an appropriate category. Would you accept Industrial automation or Automation engineering?

have a data processing category? to include the weld-project from standford

• https://github.com/weld-project/weld
• http://weld.stanford.edu/ redirect to https://weld-project.github.io/

it's written in Rust and main use cases are in Big Data Processing

conrod GUI category is a little misleading

Hey there :)

I just notices that conrod is listed under an SDL2 subheading in the GUI section. Conrod actually supports multiple backends, including SDL2, GLFW and glutin, and also allows for implementing custom backends via backend traits.

I haven't yet submitted a PR as I'm unsure how you'd wish to handle this fix. Perhaps a new "Any Platform" or "Platform Agnostic" subheading could be made? Let me know your thoughts and i'd be happy to do a PR (unless you're happy to make the fix yourself).

About Rust bindings for OpenCV

Recommend this repo that for OpenCV in rust

GSL

Hi,

I'm currenly writing (for a few months now) a binding for the GSL library here. Would it be possible to add it please ?

Add redis-rs

https://github.com/mitsuhiko/redis-rs

missing awesome badge in README.md?

Thought we should have that "awesome badge" - in README.md, or did we leave it out intenionally for some reason?

Adding collenchyma

Why not adding collenchyma ? GPU programming is important !

Moving away from a single markdown file?

Since the Markdown file has grown a bit, i am considering extracting the data to a file (maybe JSON) and generating HTML from it.

Disadvantages:

• there is an additonal generator step
• contributors might expect a Markdown file

Advantages:

• the data file could be reused easier by other projects
• entries can show up in multiple sections without duplicating data
• less boilerplate code for contributors, less possibilities for errors
• the data can be checked and enriched easier. E.g. a script could check whether the links in the data file are correct or whether projects have (now) working Travis/Cargo URLs
• no manual sorting necessary anymore
• consistent output format across all entries
• the output format can be adjusted easier in the generator

rust-learning

Hi,
I have a project rust-learning which tend to aggregate all the useful resources to learn rust. I'll add a link to awesome-rust in my README.

IMO learning resources and tools/libraries should have a separate repos because of maintenance issues and too much content to manage.
I would like to know your point of view about that, I saw that you have a "resources" section too.

Add "trust"

trust is a "Travis CI and AppVeyor template to test your Rust crate on 5 architectures and publish binary releases of it for Linux, macOS and Windows"

Would a PR for this be welcome?

Split categories in to files?

Wondering if it would be a good idea to split categories in to separate md files?

Reason being, it may become harder to keep track and/or edit later.

Cebuano Localization

Hi Good Day! I would like to request to contribute in your project. Please allow me to have translation in Cebuano. Hoping for your positive response!
Thank You!

add ripgrep

https://github.com/BurntSushi/ripgrep

Add Neon

Would a pr for Neon be welcome?

Add bindings to Nuklear

https://github.com/snuk182/nuklear-rust
Bindings to the Nuklear immediate GUI library.

Remove Rust CI

As far as I know, Rust CI is dead. Additionaly, rust-ci.org is now redirecting to crates.io.

Transfer

I'd like to handover the repository to someone else.
@steveklabnik, @nasa42 maybe you have a suggestion.

I'd love it if it could stay:

• useful
• clutter-free
• sorted
• single page
• uncommercial

I'd love it if it gained (automatic) QA to ensure:

• working links
• consistent format
• removing stale projects

Consider removing JustSid/AfterglowIntelliJ

The IntelliJ plugin JustSid/AfterglowIntelliJ has nothing to do with Rust programming, and is not even written in Rust. It should be removed from this list.
It is rather a theme for IntelliJ and the only thing it comes with regarding rust is a file icon ...

Validate pull requests with Travis

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

Examples
This tool is currently being used by https://github.com/dkhamsing/open-source-ios-apps and https://travis-ci.org/matteocrippa/awesome-swift

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information 😄

add new resource to learn rust

http://cis198-2016s.github.io/schedule/

Fix build #3 by correct errors found by awesomebot

https://travis-ci.org/rust-unofficial/awesome-rust/builds/244830080

We shouldn't normally need to do this with future pull requests, now that we've enabled on travis.

I would also make the suggestion that all maintainers should start using PR rather than editing the file directly so we can all utilise awesomebot validation via travis.

cc @kud1ing @Manishearth @luciusmagn @Freyskeyd

Add Sodiumoxide

Please add https://github.com/dnaq/sodiumoxide to the Cryptography section.

Add NNTP client

https://github.com/mattnenterprise/rust-nntp

Add contribution guidelines

With clear guidelines on when and how to contribute.

See https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines

add rsk to "development tools"

Hello, love this list!

I have released the beta version, which is quite stable and snappy, of rsk: the requirements tracking tool made for developers. It is ultra simple to use, is text based so it can be tracked in your repository, and has a full featured interactive tutorial built into the tool. Check it out!

https://github.com/vitiral/rsk

It would be great if it could be added to your list! Thanks a bunch!

Quick update Name

https://github.com/daniel-Q6wUOI/zap -> https://github.com/oltdaniel/zap

Just renamed the account

Add `zap`

zap is a lightning fast web framework that is up to 2.8times faster than iron which is based on hyper.

Currently the 0.0.1 release had been done, and there will come a lot of future add-ons and optimizations to reach the 3times faster mark.

URL: https://github.com/oldaniel/zap

Sōzu, a HTTP reverse proxy

https://github.com/sozu-proxy/sozu

Add a license

This repo misses a license. You could use https://github.com/sindresorhus/awesome#license as inspiration.

please include jwt and imap

please include

a) imap library https://github.com/GildedHonour/atarashii_imap
b) jwt https://github.com/GildedHonour/frank_jwt

Add ArcadeRS tutorial

http://jadpole.github.io/arcaders/arcaders-1-0

A tutorial on writing an old-school scrolling shooter in Rust. Not my article, but it's pretty in depth.

Split templating engines category into "static" and "dynamic"

Not the best names, but some template engines can load templates at run-time, whereas others work at compile-time (because they use plugins or macros, like Horrorshow). This is a pretty big distinction that should probably be mentioned.

broken link

thoughtram/clog — a conventional changelog port (generates a changelog from git metadata)

The link on "a conventional changelog port" seems broken.

Habitat

https://www.habitat.sh/

Somebody might want to add Habitat, its worth a look - an alternative to AppImage and so on

Incorrect game engine entry

As of early 2016, Amethyst is no longer a lone-developer project. 😄 As such, the new GitHub repository is located at http://github.com/amethyst/amethyst, the website is https://www.amethyst.rs/, and the correct Travis CI shield is at https://travis-ci.org/amethyst/amethyst.svg?branch=master.

Also, in regards to rust.libhunt.com, which I assume this repository is affiliated with, I don't think there should be a Game Development/Amethyst sub-category. The only entries in there are amethyst and an unrelated crate called challonge-rs.

I'm willing to make a PR to fix these issues. That said, this is an excellent list! Keep up the great work.

Logging section?

As section of libraries or subsection in development tools, or subsection in Testing (less appropriate).

some suggestions

Please consider the following crates:

• pem For parsing data from PEM files
• cargo-ebuild For creating Gentoo ebuilds from crates.io packages
• cargo-bitbake For creating Yocto recipes from crates.io packages

Place more items in "Game development" category

Currently, the "Game development" category does not include Rust's SDL or SFML bindings, which instead are found under the "GUI" category. Since SDL and SFML are very prominent libraries for game development (arguably moreso than they are for GUI development), it would make more sense to have them placed under that section, or at least duplicated to it.

Add Racer

https://github.com/phildawes/racer

Mark required rustc version

Something like:

It would be nice to get crates.io support for this (rust-lang/crates.io#168) but that might take a while.

Consider removing scirust

It doesn't build nowdays and doesn't seem to be supported any more...

Add Pijul

Pijul is a distributed version control system based on a new theory of patches, and entirely implemented in Rust.

Add hdfs-rs (HDFS Client)

https://github.com/hyunsik/hdfs-rs
http://hyunsik.github.io/hdfs-rs/hdfs/index.html

It may be proper in distributed system.

AwesomeOpenSource

We are creating a github org for all awesome open source repos. I am working with a few individuals who are also managing their own awesome repos, and I think to gain more traction we need to work together. What are your thoughts about collectively moving your awesome repos to https://github.com/AwesomeOpenSource

The idea is that visibility for these repos would be increased due to more traffic to the org. What are your thoughts? Let me know if there is anything you'd like to discuss!

Add POP3 client

https://github.com/mattnenterprise/rust-pop3