| commit | 06db47750e7de944b36a60d4028fbdf73e92cccc | [log] [tgz] |
|---|---|---|
| author | Adam Bender <abender@gmail.com> | Sun Mar 09 22:12:14 2025 -0700 |
| committer | Gopher Robot <gobot@golang.org> | Tue Mar 11 15:15:30 2025 -0700 |
| tree | 52230745080ccf1c83195a03a447963944cf1151 | |
| parent | c8feb7c10b44d2a4ae2cf7a37bfda3e390a3f037 [diff] |
wiki: Prefer "white space" over "whitespace" Both "whitespace" and "white space" are used in the codebase. There doesn't seem to be an external consensus as to which is better (see https://github.com/orgs/mdn/discussions/382 for a discussion). https://www.unicode.org/versions/Unicode16.0.0/UnicodeStandard-16.0.pdf (warning: 12 MB file) consistently uses "whitespace", but the character property is "White_Space". Regardless of which, if any, term is deemed to be preferred, I believe the Go codebase should at least be consistent. This change was prompted by browsing pkg.go.dev/strings and searching for "whitespace", which found only strings.FieldsSeq, not strings.Fields, which uses "white space". Change-Id: I0ad850831e4359a8c84afffa4ad86373e14133ca Reviewed-on: https://go-review.googlesource.com/c/wiki/+/656315 Reviewed-by: Rob Pike <r@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org> Auto-Submit: Ian Lance Taylor <iant@golang.org>