diff options
author | 2022-08-16 10:27:33 -0700 | |
---|---|---|
committer | 2022-08-17 10:43:13 -0700 | |
commit | d079e0b2708ce0f4cce470db929f28dd8d2b0e80 (patch) | |
tree | e8cdb4a59bd88411a262a1d91bd75def56cc4de2 /finder | |
parent | 852d0c48593fb2a17d301d7274edac907e8e194f (diff) |
Reformat build/soong for go 1.19
Test: none
Change-Id: I132368f0fcbdb5ea088b5b84dbe4ccfdd9e94cad
Diffstat (limited to 'finder')
-rw-r--r-- | finder/finder.go | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/finder/finder.go b/finder/finder.go index c5196c8de..054ccd639 100644 --- a/finder/finder.go +++ b/finder/finder.go @@ -736,15 +736,15 @@ func (f *Finder) parseCacheEntry(bytes []byte) ([]dirFullInfo, error) { // because we know this separator won't appear in the json that we're parsing. // // The newline byte can only appear in a UTF-8 stream if the newline character appears, because: -// - The newline character is encoded as "0000 1010" in binary ("0a" in hex) -// - UTF-8 dictates that bytes beginning with a "0" bit are never emitted as part of a multibyte -// character. +// - The newline character is encoded as "0000 1010" in binary ("0a" in hex) +// - UTF-8 dictates that bytes beginning with a "0" bit are never emitted as part of a multibyte +// character. // // We know that the newline character will never appear in our json string, because: -// - If a newline character appears as part of a data string, then json encoding will -// emit two characters instead: '\' and 'n'. -// - The json encoder that we use doesn't emit the optional newlines between any of its -// other outputs. +// - If a newline character appears as part of a data string, then json encoding will +// emit two characters instead: '\' and 'n'. +// - The json encoder that we use doesn't emit the optional newlines between any of its +// other outputs. const lineSeparator = byte('\n') func (f *Finder) readLine(reader *bufio.Reader) ([]byte, error) { |