-
$ cat test.go
package p
var x = (foo /* foo */ + bar /* bar */)
$ gofmt -r 'foo->bla' test.go
package p
var x = (bla + bar /* bar */)
Instead it should print:
package p
var x = (bla /* foo *…
-
It is well understood that users shouldn't enforce Go source code formatting
with `go/format`. This is documented in its godoc, but also repeated in Go
release notes: https://tip.golang.org/doc/go1.…
mvdan updated
3 years ago
-
```
What steps will reproduce the problem?
1. Try to build
2. There is error log on event log box
What is the expected output? What do you see instead?
When I build source codes, I can see "gofmt wai…
-
Should `go fmt` be used instead of `gofmt`? Looks like these are 2 different tools.
-
Documentation is not same:
```
gofmt -h
usage: gofmt [flags] [path ...] -cpuprofile string write cpu profile to th…
-
We have a few lint-style checks for `gofmt` and `go vet` which are implemented as `sh_test`s. We had a `data` dependency on `@io_bazel_rules_go_toolchain//:toolchain`, which brought `external/io_bazel…
ixdy updated
2 months ago
-
To make `gunk format` play nicely with other code formatters, and to be more familiar to Go developers, command line flags `-w` and `-s` should be added to the `format` command enabling the same behav…
-
[This failed build](https://travis-ci.org/ampproject/amp-by-example/builds/201355646) shows that
test -z $(gofmt -l $(find . -name '*.go'))
doesn't actually "list files whose formatting diff…
dandv updated
7 years ago
-
currently if it gets multiple diffs for the same file it will only write the first
-
LiteIDE Version: X33.1
Go Version: 1.9
OS: Linux amd64
There used to be an option unfer the GolangFmt options to "use goimports" instead of go fmt. That option is no longer there and now just has…