project-error-handling
mdBook
Our great sponsors
project-error-handling | mdBook | |
---|---|---|
10 | 100 | |
263 | 16,669 | |
0.0% | 2.5% | |
0.0 | 8.6 | |
almost 2 years ago | 9 days ago | |
Rust | ||
Apache License 2.0 | Mozilla Public License 2.0 |
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.
project-error-handling
-
Hey Rustaceans! Got a question? Ask here (16/2023)!
This actually is an example of where the compiler errors could (or should have) maybe provided more help or even the potential solution, it might be worth submitting this to the error handling group.
-
A guide to error handling in Rust
If anyone's interested in helping to shape the future of Rust's built-in error-handling story, there's an error handling project group that's been doing great work recently, e.g. the major effort to move the Error trait into libcore ( https://github.com/rust-lang/project-error-handling/issues/3 ) and stabilizing std::backtrace. You can follow along or get involved via the #project-error-handling channel on the Rust zulip: https://rust-lang.zulipchat.com/
-
Update on the effort to move the Error trait into core
Getting it into alloc would enable usage in a LOT more contexts, like WASM and kernel code. Does this need a distinct tracking issue outside the ticket for moving it to core or would that just add more administrata?
-
What do you NOT like about Rust?
without trolling https://github.com/rust-lang/project-error-handling exist and is far from having strong conclusion and anyway I will always favor enum Error anyway however I like the idea to have a opaque box in the enum for "this is a opaque error you can't deal with as a user of my api"
-
Possible ergonomic option for error handling: what features are needed for this to work?
IIRC, the Error Handling Project Group is aware of these ideas. If this kind of thing interests you and you want to contribute, you should look into getting involved with that group.
-
Rust: Enums to Wrap Multiple Errors
> you should have the underlying message of the std::io::Error
This is a point of debate[1] among the error-handling working group.
[1]: https://github.com/rust-lang/project-error-handling/issues/4...
-
Ergonomic error handling with Rust
Focusing on good error messages has permeated throughout the community. There's even the Error Handling Project Group if you weren't convinced how committed the language designers are to getting this right. There are a number of techniques we can use to make our errors more informative. Along the way, we will discuss the crates that can help.
-
A Small Rust 2021 Change Return Display From Main
The Error Handling Working Group is looking at potential breaking changes for embedded users. Maybe you could work within that group?
mdBook
- Doks – Build a Docs Site
-
Ask HN: How do you organize software documentation at work?
I'm responsible for a number of Java products. I try to provide high-quality Javadoc for all public library interfaces, library user's guides where appropriate, and development guides for applications. The latter two take the form of MDBook documents (https://rust-lang.github.io/mdBook/), with the document source living in the GitHub repo so that it's tied to the particular software release in a natural way.
-
Outline: Self hostable, realtime, Markdown compatible knowledge base
My org has used mdBook: https://rust-lang.github.io/mdBook/ (That link is itself a rendered mdBook, so that'll give you an idea of the feature set.)
(While it's definitely a Rust "thing", if you just have a set of .md files, all you need is a "SUMMARY.md" (which contains the ToC) and a small config file; i.e., you don't have to have any Rust code to use it, and it works fine without. We document a large, mostly non-Rust codebase with it.)
-
Ask HN: Best tools for self-authoring books in 2023?
If you want the lowest friction, open source, easily extensible Markdown to Web, Kindle, PDF, etc. tool, highly recommend mdBook: https://github.com/rust-lang/mdBook it’s written in Rust, but you don’t have to know any Rust to use it. And then wing is all CSS; for which there are many good (free) themes.
- Early performance results from the prototype CHERI ARM Morello microarchitecture
- FLaNK Stack for 4th of July
- MdBook – A command line tool to create books with Markdown
- MdBook Create book from Markdown files. Like Gitbook but implemented in Rust
-
MdBook – Create book from Markdown files. Like Gitbook but implemented in Rust
Interesting enough there seems to be an open PR for that: https://github.com/rust-lang/mdBook/pull/1918
What are some alternatives?
serenity - A Rust library for the Discord API.
gitbook - The open source frontend for GitBook doc sites
PyO3 - Rust bindings for the Python interpreter
MkDocs - Project documentation with Markdown.
eyre - A trait object based error handling type for easy idiomatic error handling and reporting in Rust applications
Wiki.js - Wiki.js | A modern and powerful wiki app built on Node.js
goformat - Alternative to gofmt with configurable formatting style (indentation etc.)
bookdown - Authoring Books and Technical Documents with R Markdown
rust-cpython - Rust <-> Python bindings
obsidian-releases - Community plugins list, theme list, and releases of Obsidian.
cargo-leptos - Build tool for Leptos (Rust)
Docusaurus - Easy to maintain open source documentation websites.