By tagging every clutz-generated file with a comment, tsickle can
then use this to identify clutz output.
Note that emitComment() output doesn't show up in tests, so this doesn't
affect any tests. I think it's not very valuable to have this test
baselines include this comment anyway.
By tagging every clutz-generated file with a comment, tsickle can then use this to identify clutz output.
Note that emitComment() output doesn't show up in tests, so this doesn't affect any tests. I think it's not very valuable to have this test baselines include this comment anyway.