goformat VS docs.rs

Likewise, gofmt implementing what you argue for resulted in the creation of goformat. There's a limit to how much you can force people on these things and, more importantly, there are formatting decisions which are more than mere bikeshedding in the eyes of the programmers to the point where they consider it more productive to maintain the formatting by hand if that's what it takes.

I'm the guy who would only run rustfmt once every week or so, when my codebase was in a clean state where I could use git gui to cherry-pick the changes that were in line with my stubborn insistence on my own style and revert the rest. I'm also the guy who would have considered writing goformat if someone else didn't.

Enough people disagree with that for goformat to exist.

Same. I used to insist on cargo +nightly rustfmt and a massive stable of "I don't have a portrait-oriented monitor" rustfmt.toml tweaks which I'd only apply when I have a clean git gui on hand to cherry-pick away unwanted changes, but I've mellowed out and the rustfmt handling of things like assert! has evolved so, now, I just put use_small_heuristics = "Max" in my rustfmt.toml as an analogue to the people who choose goformat over gofmt.

anyways, regardless of what I think, perhaps this library could help? Or at least be a good starting point to build your own: https://github.com/mbenkmann/goformat

You'd prefer that people like me follow the road the Go ecosystem did and write goformat as a replacement for gofmt or just continue to hand-format everything?

Because Go syntax is ridiculously simple, there's not much room for opinion. And even considering that, there is already an alternative gofmt with custom options.

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.

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...

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.

📝 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.

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.

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.

docs.rs also downloads you crate automatically to generate docs and I would guess lib.rs does something similar

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

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.