Fix lint warn #2673
k1LoWci.yml
on: pull_request
Test
4m 42s
Lint
1m 32s
Matrix: Run on each OS
Annotations
5 errors
|
[gostyle] eval.go#L23:
eval.go#L23
[gostyle.repetition] The compiler always knows the type of a variable, and in most cases it is also clear to the reader what type a variable is by how it is used. It is only necessary to clarify the type of a variable if its value appears twice in the same scope. (ref: https://google.github.io/styleguide/go/decisions#variable-name-vs-type ): maxUint<-[uint]->uint
|
|
[gostyle] eval.go#L24:
eval.go#L24
[gostyle.repetition] The compiler always knows the type of a variable, and in most cases it is also clear to the reader what type a variable is by how it is used. It is only necessary to clarify the type of a variable if its value appears twice in the same scope. (ref: https://google.github.io/styleguide/go/decisions#variable-name-vs-type ): maxInt<-[int]->int
|
|
Lint:
eval.go#L23
[gostyle.repetition] The compiler always knows the type of a variable, and in most cases it is also clear to the reader what type a variable is by how it is used. It is only necessary to clarify the type of a variable if its value appears twice in the same scope. (ref: https://google.github.io/styleguide/go/decisions#variable-name-vs-type ): maxUint<-[uint]->uint
|
|
Lint:
eval.go#L24
[gostyle.repetition] The compiler always knows the type of a variable, and in most cases it is also clear to the reader what type a variable is by how it is used. It is only necessary to clarify the type of a variable if its value appears twice in the same scope. (ref: https://google.github.io/styleguide/go/decisions#variable-name-vs-type ): maxInt<-[int]->int
|
|
Lint
Process completed with exit code 1.
|