rustfmt
goreleaser
rustfmt | goreleaser | |
---|---|---|
57 | 60 | |
5,773 | 13,072 | |
1.1% | 1.9% | |
8.8 | 9.8 | |
4 days ago | 7 days ago | |
Rust | Go | |
Apache License 2.0 | 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.
rustfmt
-
You can't do that because I hate you
The author provides very surface-level criticism of two Rust tools, but they don't look into why those choices were made.
With about five minutes of my time, I found out:
wrap_comments was introduced in 2019 [0]. There are bugs in the implementation (it breaks Markdown tables), so the option hasn't been marked as stable. Progress on the issue has been spotty.
--no-merge-sources is not trivial to re-implement [1]. The author has already explained why the flag no longer works -- Cargo integrated the command, but not all of the flags. This commit [2] explains why this functionality was removed in the first place.
Rust is open source, so the author of this blog post could improve the state of the software they care about by championing these issues. The --no-merge-sources error message even encourages you to open an issue, presumably so that the authors of Cargo can gauge the importance of certain flags/features.
You could even do something much simpler, like adding a comment to the related issues mentioning that you ran into these rough edges and that it made your life a little worse, or with a workaround that you found.
Alternatively, you can continue to write about how much free software sucks.
[0]: https://github.com/rust-lang/rustfmt/issues/3347
[1]: https://github.com/rust-lang/cargo/pull/10344
[2]: https://github.com/rust-lang/cargo/commit/3842d8e6f20067f716...
-
Let else will finally be formatted by rustfmt soon
The new style still supports single line let-else, and there is a configuration parameter to make it be on one line also for longer lines.
-
Is rustfmt abandoned? Will it ever format `let ... else` syntax?
It seems there is an issue about this dating all the way back from 2018 but yet it still hasn't been fixed.
-
Hey Rustaceans! Got a question? Ask here (22/2023)!
However since 4179 recent versions should merge configuration files. Not sure what the details / specifics are but if just ignoring the file entirely is not good enough you might give it its own directory and rustfmt.toml file and see if that works.
-
Rustfmt refusing to work with certain functions.
Could this be be #3863 - Gives up on chains if any line is too long? It might not be, because I can't see a specific "line" that's too long to format, but there's more detail about the exact problem in the issue.
-
Rust Tips and Tricks #PartOne
Rustfmt is a tool that formats Rust code in compliance with style guidelines. Its name precisely reflects its purpose. To install rustfmt, you can run rustup component add rustfmt. Once installed, you can execute cargo fmt to format Rust code in your workspace. If you require further information, you can visit rustfmt’s GitHub repository.
-
What are some good practices when writing rust?
code must be formatted with rustfmt.
- HTML Limpo
-
Hey Rustaceans! Got a question? Ask here (5/2023)!
Yes, some cases are not yet supported (https://github.com/rust-lang/rustfmt/issues/4914).
-
How do I stop RustFmt from turning this…
Just FYI, the let-else suggestions will only work until rustfmt settles on a format for it. So you may be surprised when this happens and it suddenly changes.
goreleaser
-
Show HN: Docker-phobia: Analyze Docker image size with a treemap
> This is a much faster way than setting up Github Actions to build an executable for every possible platform on every release
It's not even that hard. Just use GoReleaser.
https://goreleaser.com/
-
FOSDEM 2024 - Summary and Reflections
I also got my eyes on GoReleaser, which I will use in my (Go) projects.
- Distribuindo uma aplicação Go sem o Docker
- goreleaser: Deliver Go binaries as fast and easily as possible
- Goreleaser
-
Build an Open Source Project: Behind the Scenes
With "xq", I went even further and automated the release process using GoReleaser. To publish a new release, the only thing I need is to create and push the Git tag. The corresponding GitHub Action will trigger a release process, and GoReleaser prepares the binaries and changelog based on declared conventions. The result has a high level of predictability, and no manual work is required.
-
How to start a Go project in 2023
Things I can't live without in a new Go project in no particular order:
- https://github.com/golangci/golangci-lint - meta-linter
- https://goreleaser.com - automate release workflows
- https://magefile.org - build tool that can version your tools
- https://github.com/ory/dockertest/v3 - run containers for e2e testing
- https://github.com/ecordell/optgen - generate functional options
- https://golang.org/x/tools/cmd/stringer - generate String()
- https://mvdan.cc/gofumpt - stricter gofmt
- https://github.com/stretchr/testify - test assertion library
- https://github.com/rs/zerolog - logging
- https://github.com/spf13/cobra - CLI framework
FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb
We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers
-
What is recommended build tool and process for go project that contains multiple libraries, apis and executables?
Goreleaser is nice. https://goreleaser.com/
-
Best practices for distributing and updating a Go CLI on Linux?
I use goreleaser for packaging my binaries. I'm not currently doing RPM, but it does a lot of services and if you don't hunker down on a single solution, it might help with keeping your releases up to date/in sync.
-
Looking for projects ideas for experienced devops engineers
There's some packaging issues, for example, we've always wanted to publish deb/rpm packages, but never got around to adding it to either promu or completely switching our build tooling over to GoReleaser.
What are some alternatives?
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
Task - A task runner / simpler Make alternative written in Go
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
gron - gron, Cron Jobs in Go.
rust-analyzer - A Rust compiler front-end for IDEs
go-torch
Rust for Visual Studio Code
godropbox - Common libraries for writing Go services/applications.
vscode-rust
hub - A command-line tool that makes git easier to use with GitHub.
sublime-rust - The official Sublime Text 4 package for the Rust Programming Language
goreporter - A Golang tool that does static analysis, unit testing, code review and generate code quality report.