You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The very first one in the dump-configuration output, fileScopedDeclarationPrivacy, doesn't appear in the configuration documentation, and it has what looks like a pretty drastic effect, and doesn't accept what I'm guessing is the most obvious setting internal. /cc @allevato
The text was updated successfully, but these errors were encountered:
That option controls which visibility modifier to use (private or fileprivate) for declarations already using one of those at file-scope. That is, private and/or fileprivate declarations will be forced to be one or the other. This is to force consistency where—with the exception of extension decls, which are excluded from this—the two have the same effective visibility.
internal isn't supported since that would change the effective visibility of file-scoped decls.
Re: the larger documentation issue, we should just adopt DocC like I want to do for the rules so that the source code is the source of truth and we generate everything from that.
The very first one in the
dump-configuration
output,fileScopedDeclarationPrivacy
, doesn't appear in the configuration documentation, and it has what looks like a pretty drastic effect, and doesn't accept what I'm guessing is the most obvious settinginternal
. /cc @allevatoThe text was updated successfully, but these errors were encountered: