blessed-rs
docs.rs
blessed-rs | docs.rs | |
---|---|---|
6 | 141 | |
1,179 | 945 | |
- | 0.5% | |
6.7 | 9.5 | |
about 1 month ago | 5 days ago | |
HTML | Rust | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
blessed-rs
-
Crate List - Blessed.rs
I opened a PR to correct this.
-
Blessed.rs – An unofficial guide to the Rust ecosystem
This is my project (although I didn't submit this to HN), AMA
I consider quite incomplete at this point (but hopefully already useful). There are several categories of crate that just aren't covered yet (suggestions very welcome, either here or on the github repo https://github.com/nicoburns/blessed-rs).
I'd also like to add more hand curated content such as:
- Installation and developer environment setup
-
What crates are considered as de-facto standard?
No, it's hand curated (see https://github.com/nicoburns/blessed-rs for source). There is a separate project https://lib.rs that takes a more automated approach (you can browse the most downloaded crates by count).
-
Enable VSCode lifetimes elisions hints to learn about lifetimes
This sounds like the sort of thing I created https://blessed.rs to host (source: https://github.com/nicoburns/blessed-rs). I never really launched it, so it's a bit incomplete atm. But the idea is that it's a guide to all the stuff that can't be in the official docs (because that would be favouritism), but that every rust developer ought to know.
-
I want to improve project management practices for the Rust Lang team!
I've been quietly working on something like this over at https://blessed.rs (source: https://github.com/nicoburns/blessed-rs) At the moment it's just a curated list of crates (and still a fairly short one at that), but the vision is very much to be a go-to knowledge base for Rust, a community managed counterpart to the official website. I've been putting off an announcement until it's more ready, but perhaps it's better to get it out there.
-
Q about Rust Microservices
My dockerfile: https://github.com/nicoburns/blessed-rs/blob/main/Dockerfile.build
docs.rs
-
Using GenAI to improve developer experience on AWS
Working in combination with CodeWhisperer in your IDE, you can send whole code sections to Amazon Q and ask for an explanation of what the selected code does. To show how this works, we open up the file.rs file cloned from this GitHub repository. This is part of an open source project to host documentation of crates for the Rust Programming Language, which is a language we are not familiar with.
-
TSDocs.dev: type docs for any JavaScript library
Looks like a great initiative – I wish there was a reliable TS/JS equivalent of https://docs.rs (even considering rustdoc's deficiencies[1]).
I went through this exercise recently and so far my experience with trying to produce documentation from a somewhat convoluted TS codebase[2] has been disappointing. I would claim it's a consequence of the library's public (user-facing) API substantially differing from how the actual implementation is structured.
Typedoc produces bad results for that codebase so sphinx-js, which I wanted to use, doesn't have much to work with. I ultimately documented things by hand, for now, the way the API is meant to be used by the user.
Compare:
https://ts-results-es.readthedocs.io/en/latest/reference/api...
vs
https://tsdocs.dev/docs/ts-results-es/4.1.0-alpha.1/index.ht...
-
How did I need to know about feature rwh_05 for winit?
Rust Search Extension adds a section on docs.rs menubar which lists the features of a crate in a nice and easy to access format.
-
Embassy on ESP: GPIO
📝 Note: At the time of writing this post, I couldn't really locate the init function docs.rs documentation. It didn't seem easily accessible through any of the current HAL implementation documentation. Nevertheless, I reached the signature of the function through the source here.
-
First Rust Package - Telegram Notification Framework (Feedback Appreciated)
Rust Crates are a Game-Changer 🎮:The ease of releasing a crate with `cargo publish` and the convenience of rolling out new versions amazed me. The auto-generated docs on Docs.rs. is an amazing tool, especially with docstring formatting. Doc tests serve as a two-fold tool for documenting the code and ensuring it's up-to-date.
-
Grimoire: Open-Source bookmark manager with extra features
I've found I manually type out certain subsets of URLs where possible[0], maybe that's subconsciously associated with my impression that Google Search results have gotten worse and worse over the years.
[0] https://en.wiktionary.org/wiki/ and https://docs.rs/ come to mind.
-
Released my first crate ~20 hours ago; already downloaded 12 times. Who would know about it?
docs.rs also downloads you crate automatically to generate docs and I would guess lib.rs does something similar
- Docs.rs Is Down
-
Managed to land a junior role need help!
There are also a few key sites you'll want to keep in your back pocket at all times: - The Standard Library Documentation has complete documentation for every std library function in Rust - crates.io is a repository for all third-party packages, and docs.rs has human-readable documentation for the overwhelming majority of them - The Rust Cookbook has some code examples for common tasks you may need to perform - Make sure you are using clippy, which is available through Rustup and can be run with cargo clippy as a replacement to cargo check, it adds additional lints for your Rust code and is very helpful for teaching many of the best practices
-
How do you like code documentation inline in the source code vs. as separate guides, or how would you do it?
OTOH, source-code-generated-docs normalize how code docs are, like the rust docs.rs paradigm, so it sort of forces or encourages package creators/maintainers to write docs.
What are some alternatives?
argparse-rosetta-rs - Comparing argparse APIs
crates.io - The Rust package registry
serde-regex - A serde wrapper that allows to (de)serialize regular expressions
serenity - A Rust library for the Discord API.
tui-input - TUI input library supporting multiple backends, tui-rs and ratatui
config-rs - ⚙️ Layered configuration system for Rust applications (with strong support for 12-factor applications).
bevy - A refreshingly simple data-driven game engine built in Rust
awesome-bevy - A collection of Bevy assets, plugins, learning resources, and apps made by the community
rust - Empowering everyone to build reliable and efficient software.
bevy-website - The source files for the official Bevy website
cargo-readme - Generate README.md from docstrings
rfcs - Suggest changes to Bevy and view accepted designs