|
1 | 1 | # Commands |
2 | 2 |
|
3 | | -Mathlib version: `6d297a4172e6c37d3bf82e68924c45d72621ac5d` |
| 3 | +Mathlib version: `955e8f97a6372ceeeb97f4acc87f71ae1fea7d85` |
4 | 4 |
|
5 | 5 | ## \#adaptation_note |
6 | 6 | Defined in: `adaptationNoteCmd` |
@@ -1269,7 +1269,7 @@ Defined in: `commandDeclare_uint_theorems_` |
1269 | 1269 |
|
1270 | 1270 |
|
1271 | 1271 | ## deprecate to |
1272 | | -Defined in: `Mathlib.Tactic.DeprecateMe.commandDeprecate_to______` |
| 1272 | +Defined in: `Mathlib.Tactic.DeprecateTo.commandDeprecate_to______` |
1273 | 1273 |
|
1274 | 1274 | Writing |
1275 | 1275 | ```lean |
@@ -1367,7 +1367,7 @@ end Evening.Sky |
1367 | 1367 | #check Evening.Sky.star |
1368 | 1368 | ``` |
1369 | 1369 |
|
1370 | | -## export private |
| 1370 | +## export |
1371 | 1371 | Defined in: `Lean.Elab.Command.exportPrivate` |
1372 | 1372 |
|
1373 | 1373 | The command `export private a b c in foo bar` is similar to `open private`, but instead of opening |
@@ -1712,6 +1712,19 @@ can also refer to typeclass instance variables by type using the syntax `omit [T |
1712 | 1712 | which case all instance variables that unify with the given type are omitted. `omit` should usually |
1713 | 1713 | only be used in conjunction with `in` in order to keep the section structure simple. |
1714 | 1714 |
|
| 1715 | +## open |
| 1716 | +Defined in: `Lean.Elab.Command.openPrivate` |
| 1717 | + |
| 1718 | +The command `open private a b c in foo bar` will look for private definitions named `a`, `b`, `c` |
| 1719 | +in declarations `foo` and `bar` and open them in the current scope. This does not make the |
| 1720 | +definitions public, but rather makes them accessible in the current section by the short name `a` |
| 1721 | +instead of the (unnameable) internal name for the private declaration, something like |
| 1722 | +`_private.Other.Module.0.Other.Namespace.foo.a`, which cannot be typed directly because of the `0` |
| 1723 | +name component. |
| 1724 | + |
| 1725 | +It is also possible to specify the module instead with |
| 1726 | +`open private a b c from Other.Module`. |
| 1727 | + |
1715 | 1728 | ## open |
1716 | 1729 | Defined in: `Lean.Parser.Command.open` |
1717 | 1730 |
|
@@ -1827,19 +1840,6 @@ section |
1827 | 1840 | end |
1828 | 1841 | ``` |
1829 | 1842 |
|
1830 | | -## open private |
1831 | | -Defined in: `Lean.Elab.Command.openPrivate` |
1832 | | - |
1833 | | -The command `open private a b c in foo bar` will look for private definitions named `a`, `b`, `c` |
1834 | | -in declarations `foo` and `bar` and open them in the current scope. This does not make the |
1835 | | -definitions public, but rather makes them accessible in the current section by the short name `a` |
1836 | | -instead of the (unnameable) internal name for the private declaration, something like |
1837 | | -`_private.Other.Module.0.Other.Namespace.foo.a`, which cannot be typed directly because of the `0` |
1838 | | -name component. |
1839 | | - |
1840 | | -It is also possible to specify the module instead with |
1841 | | -`open private a b c from Other.Module`. |
1842 | | - |
1843 | 1843 | ## proof_wanted |
1844 | 1844 | Defined in: `«proof_wanted»` |
1845 | 1845 |
|
|
0 commit comments