Cloc has problems with */* in Go about cloc HOT 3 CLOSED

cloc --strip-str-comments test.go gives

-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Go                               1              2              0             17
-------------------------------------------------------------------------------

You'll probably always want to use --strip-str-comments when dealing with codebases that use combinations of * and / even though this will give cloc a small performance hit.

from cloc.

@AlDanial Thank you for you comment. Please, see this example:

foo: = `*/*`
a: = 10
b: = 20
foo: = `*/*`

Result:

github.com/AlDanial/cloc v 1.99  T=0.01 s (121.9 files/s, 609.4 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Go                               1              1              3              1
-------------------------------------------------------------------------------

See https://stackoverflow.com/questions/46917331/what-is-the-difference-between-backticks-double-quotes-in-golang

from cloc.