llir / llvm

68%

master: 63%

LAST BUILD ON BRANCH stringer-update

branch: stringer-update

CHANGE BRANCH

x

Reset

• stringer-update
• master
• coverage
• api
• lexer
• parser
• v0.1
• struct
• use
• ast
• irmerge
• exportmembers
• removenamedtype
• floats
• dev
• v0.2
• v0.2.1
• v0.3.0-pre1
• v0.3.0-pre2
• readme
• pwaller/pass-asm-by-value
• v0.3.0-pre3
• the-big-cleanup
• v0.3.0-pre4
• sumtype
• memprofile-l-tm
• v0.3.0-pre5
• v0.3.0-pre6
• metadata
• fix-unused-y-param
• type-checking
• type-check-insertvalue
• type-check-trunc
• type-check-store
• v0.3.0-pre7
• parent
• natsort
• travis
• f-31/powerpc128float
• v0.3.0
• f-118
• refs/tags/v0.3.1
• refs/tags/v0.3.2
• t-150
• ci
• f-154

Build # 999

Build Type

Pull #80

travis-ci

Committed by web-flow

Commit Message

Update x/tools/cmd/stringer

As of
https://github.com/golang/tools/commit/63e6ed925
stringer includes a compile time check that the constants have not changed since the last run.

I just did a rebuild of `go generate` and ended up with this large unwanted diff, so I think it is probably best to stay up-to-date with this tool.

As far as I see, this has little impact on anyone other than llvm/llir devs, who just need to make sure they keep cmd/stringer uptodate.

Pull Request Pull Request #80: Update x/tools/cmd/stringer

Run Details

11 of 11 new or added lines in 1 file covered. (100.0%)

8708 of 12726 relevant lines covered (68.43%)

69757.48 hits per line