"Since the sequence U+FEFF is exceedingly rare at the beginning of a
regular non-Unicode text file, it can serve as an implicit marker or
signature to identify the file as a Unicode file. Applications that
read both Unicode and non-Unicode text files should use the presence
of this sequence as an indicator that the file is most likely a
Unicode file. Compare this technique to using the MS-DOS EOF marker to
terminate text files."
you may want to try a different editor?
just for test, i tried writing the 0xfeff char to the beginning of an
otherwise valid go program and got the following error:
t.go:1: invalid identifier character 0xfeff
t.go:1: package statement must be first
is that what you're seeing?
-rob