Skip to content

chore: drop no-op @[expose] on optionDocs.Args - #906

Merged
robsimmons merged 1 commit into
leanprover:mainfrom
kim-em:chore/drop-noop-expose-optiondocs
Jul 7, 2026
Merged

chore: drop no-op @[expose] on optionDocs.Args#906
robsimmons merged 1 commit into
leanprover:mainfrom
kim-em:chore/drop-noop-expose-optiondocs

Conversation

@kim-em

@kim-em kim-em commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

The @[expose] attribute on optionDocs.Args in src/verso-manual/VersoManual/Docstring.lean has no effect because that file is not a module file, and it produces a @[expose] has no effect outside a module file warning on every build (including in downstream projects that build the manual). This removes the attribute; it can be reintroduced if and when the file is migrated to the module system.

The change is a no-op for compilation (the compiler itself reports the attribute has no effect), so behaviour is unchanged.

The `@[expose]` attribute on `optionDocs.Args` has no effect because
`VersoManual/Docstring.lean` is not a `module` file, and it produces a
`@[expose] has no effect outside a module file` warning on every build.
Remove it; it can be reintroduced if and when the file is migrated to the
module system.
@cursor

cursor Bot commented Jul 6, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@robsimmons

Copy link
Copy Markdown
Collaborator

This may have been a skew with nightly-testing; I'll make sure it survives in nightly-testing if that's the case

@robsimmons
robsimmons added this pull request to the merge queue Jul 7, 2026
Merged via the queue into leanprover:main with commit b8e6136 Jul 7, 2026
12 checks passed
david-christiansen pushed a commit that referenced this pull request Aug 7, 2026
The `@[expose]` attribute on `optionDocs.Args` in
`src/verso-manual/VersoManual/Docstring.lean` has no effect because that
file is not a `module` file, and it produces a `@[expose] has no effect
outside a module file` warning on every build (including in downstream
projects that build the manual). This removes the attribute; it can be
reintroduced if and when the file is migrated to the module system.

The change is a no-op for compilation (the compiler itself reports the
attribute has no effect), so behaviour is unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants