lean2/tests/lean/run/568.lean

namespace f1
  definition flip := (20:num)
end f1

namespace f2
  definition flip := (10:num)
end f2

namespace f3
  export [declaration] f1
  export - [declaration] f2
end f3

export [declaration] f1
export - [declaration] f2
fix(frontends/lean/builtin_cmds): bug in `export` command Cause: we have two different tokes to represent declarations: [decls] and [declarations] fixes #568 2015-05-02 23:01:25 +00:00			`namespace f1`
fix(tests/lean/run): adjust some tests to changes in the standard library 2015-10-13 22:39:03 +00:00			`definition flip := (20:num)`
fix(frontends/lean/builtin_cmds): bug in `export` command Cause: we have two different tokes to represent declarations: [decls] and [declarations] fixes #568 2015-05-02 23:01:25 +00:00			`end f1`

			`namespace f2`
fix(tests/lean/run): adjust some tests to changes in the standard library 2015-10-13 22:39:03 +00:00			`definition flip := (10:num)`
fix(frontends/lean/builtin_cmds): bug in `export` command Cause: we have two different tokes to represent declarations: [decls] and [declarations] fixes #568 2015-05-02 23:01:25 +00:00			`end f2`

			`namespace f3`
refactor(*): normalize metaclass names @avigad and @fpvandoorn, I changed the metaclasses names. They were not uniform: - The plural was used in some cases (e.g., [coercions]). - In other cases a cryptic name was used (e.g., [brs]). Now, I tried to use the attribute name as the metaclass name whenever possible. For example, we write definition foo [coercion] ... definition bla [forward] ... and open [coercion] nat open [forward] nat It is easier to remember and is uniform. 2015-12-28 18:30:23 +00:00			`export [declaration] f1`
			`export - [declaration] f2`
fix(frontends/lean/builtin_cmds): bug in `export` command Cause: we have two different tokes to represent declarations: [decls] and [declarations] fixes #568 2015-05-02 23:01:25 +00:00			`end f3`

refactor(*): normalize metaclass names @avigad and @fpvandoorn, I changed the metaclasses names. They were not uniform: - The plural was used in some cases (e.g., [coercions]). - In other cases a cryptic name was used (e.g., [brs]). Now, I tried to use the attribute name as the metaclass name whenever possible. For example, we write definition foo [coercion] ... definition bla [forward] ... and open [coercion] nat open [forward] nat It is easier to remember and is uniform. 2015-12-28 18:30:23 +00:00			`export [declaration] f1`
			`export - [declaration] f2`