mvdan.cc / cue
this repo has no description
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

doc/ref: clarify the relationship between exported and hidden identifiers

Quickly searching the spec for the term "hidden" does not take one
to the "exported identifiers" section, which is arguably the most
important aspect of hidden identifiers.

See the confusion in a comment in #2565, for example.

Rephrase the second and third sentences to introduce "hidden",
and also to avoid parentheses, which made the text a bit obtuse.

Signed-off-by: Daniel Martí <mvdan@mvdan.cc>
Change-Id: I50c5d75c679420437b5491f67fe3b19613c4444b
Reviewed-on: https://review.gerrithub.io/c/cue-lang/cue/+/1229636
Unity-Result: CUE porcuepine <cue.porcuepine@gmail.com>
TryBot-Result: CUEcueckoo <cueckoo@cuelang.org>
Reviewed-by: Matthew Sackman <matthew@cue.works>

Daniel Martí 367bc885 523284ff

+4 -4
+4 -4
doc/ref/spec.md
··· 1868 1868 1869 1869 An identifier of a package may be exported to permit access to it 1870 1870 from another package. 1871 - All identifiers not starting with `_` (so all regular fields and definitions 1872 - starting with `#`) are exported. 1873 - Any identifier starting with `_` is not visible outside the package and resides 1874 - in a separate namespace than namesake identifiers of other packages. 1871 + All identifiers not starting with `_` are exported, 1872 + such as regular fields or definitions starting with `#`. 1873 + Any identifier starting with `_` is hidden from other packages; 1874 + it resides in a separate namespace than namesake identifiers of other packages. 1875 1875 1876 1876 ``` 1877 1877 package mypackage