goformat
Alternative to gofmt with configurable formatting style (indentation etc.) (by mbenkmann)
project-error-handling
Error handling project group (by rust-lang)
goformat | project-error-handling | |
---|---|---|
7 | 10 | |
20 | 263 | |
- | 0.0% | |
0.0 | 0.0 | |
almost 6 years ago | about 2 years ago | |
Go | ||
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
goformat
Posts with mentions or reviews of goformat.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-19.
-
Minimalist Rust formatter as an alternative to rustfmt?
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.
-
Go is better than Rust (for networked server side applications meant for scale)?
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.
-
Why is rust so pedantic about code formatting and style?
Enough people disagree with that for goformat to exist.
-
rustfmt opt-in instead of opt-out
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.
-
Need a line-preserving gofmt tool
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
-
What do you NOT like about Rust?
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?
-
Why most rustfmt options are still unstable?
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.
project-error-handling
Posts with mentions or reviews of project-error-handling.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-17.
-
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?
What are some alternatives?
When comparing goformat and project-error-handling you can also consider the following projects:
serenity - A Rust library for the Discord API.
prettier-plugin-rust - Prettier Rust is an opinionated code formatter that autocorrects bad syntax.
PyO3 - Rust bindings for the Python interpreter
rustfmt - Format Rust code
eyre - A trait object based error handling type for easy idiomatic error handling and reporting in Rust applications
rust-cpython - Rust <-> Python bindings
cargo-leptos - Build tool for Leptos (Rust)
genemichaels - Even formats macros
leptos-language-server
goformat vs serenity
project-error-handling vs serenity
goformat vs prettier-plugin-rust
project-error-handling vs PyO3
goformat vs rustfmt
project-error-handling vs eyre
goformat vs rust-cpython
project-error-handling vs rust-cpython
goformat vs PyO3
project-error-handling vs cargo-leptos
goformat vs genemichaels
project-error-handling vs leptos-language-server