numtide/treefmt
Archived
8
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

doc: reduce use of anchors for Rust and Go in README

Browse Source 
Improves readability

Signed-off-by: Brian McGee <brian@bmcgee.ie>
This commit is contained in:
Brian McGee 2024-05-03 16:05:47 +01:00
parent c68ef405ba
commit 0a2a823ef2
Signed by: brianmcgee
GPG Key ID: D49016E76AD1E8C0
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -147,17 +147,17 @@ guidelines for more information.
You may be familiar with [Version 1], which is written in [Rust]. So, why re-write it in [Go]?
Ultimately, `treefmt` is spending most of it's time shelling out calls to the underlying formatters. This process is
just as fast/performant in [Go] as it is in [Rust].
just as fast/performant in Go as it is in Rust.
The remaining tasks are processing some cli args and parsing a config file. Do we really need something as _heavy duty_
as [Rust] for that?
as Rust for that?
Despite all this, you can make good, sane arguments for continuing with [Version 1] in [Rust] instead of a re-write.
Despite all this, you can make good, sane arguments for continuing with [Version 1] in Rust instead of a re-write.
So here's a _bad argument_.
[Brian] wanted to improve performance by moving away from a [Toml] cache file, introduce pipelines for applying multiple
formatters against the same file set, and add an extensible approach for how `treefmt` walks file systems. He knows [Go]
much better than [Rust].
formatters against the same file set, and add an extensible approach for how `treefmt` walks file systems. He knows Go
much better than Rust.
[zimbatm] thought it was a good idea too.