I'm sorry we cannot change the language, including the two forms of comments it accepts, //, and /* */.

I feel that you can use the C style /* ... */ forms equally as well as the example you showed above. Note that C code must directly preceed the import "C" line, that is there must be no linebreak between the commentary and the import declaration.

I will second ANY proposal to make included C code unmistakably distinguishable from comments.
I Personally would prefer an explicit directive like

inline{
     //  C code goes here
}

@pablochacin C is not part of the Go language specification. cgo is implemented entirely as a preprocessor and the go tool on top of the regular go compiler.

@davecheney Why cannot Cgo pimp go language and add syntaxes. It is a preprocessor. So I don't think there could be a problem.

Using the C preprocessor in Go would be great too :

{$ifdef OS}
/* Go code */
{$endif}

Or you could just move the majority of your C code to actual .c files.

@dominikh Does anything happens if there's a comment in a .c file included in Go using cgo ?

Edit: Do not forget that almost C programmers use block comments /* */, so yes, it could create errors, but not if you use line comments //.

@dominikh All cgo cares about is what you put in the .go file. You can write
// #include "foo.h"
import "C"
and put anything you like in foo.h. You can still reference things declared in foo.h using the C. syntax--see the cgo docs.

@ianlancetaylor I assume your last comment was directed at @StEvUgnIn, not me?

@StEvUgnIn et al, this issue is marked as closed. Please continue the discussion on golang-nuts. Thanks.

@dominikh Yes, sorry. Error on my part.