michael/lean2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
lean2/tests/lean/binder_overload.lean.expected.out

16 lines
575 B
Text
Raw Normal View History

chore(tests): mass-update for pp.binder_types false
2016-05-31 22:14:42 -04:00
{x ∈ S | x > 0} : set ℕ
{x ∈ s | x > 0} : finset ℕ
fix(library/tc_multigraph): avoid name collisions @avigad, @fpvandoorn, @rlewis1988, @dselsam I changed how transitive instances are named. The motivation is to avoid a naming collision problem found by Daniel. Before this commit, we were getting an error on the following file tests/lean/run/collision_bug.lean. Now, transitive instances contain the prefix "_trans_". It makes it clear this is an internal definition and it should not be used by users. This change also demonstrates (again) how the `rewrite` tactic is fragile. The problem is that the matching procedure used by it has very little support for solving matching constraints that involving type class instances. Eventually, we will need to reimplement `rewrite` using the new unification procedure used in blast. In the meantime, the workaround is to use `krewrite` (as usual).
2016-02-04 13:15:42 -08:00
@set.sep.{1} nat
chore(tests): mass-update for pp.binder_types false
2016-05-31 22:14:42 -04:00
(λ x,
fix(library/tc_multigraph): avoid name collisions @avigad, @fpvandoorn, @rlewis1988, @dselsam I changed how transitive instances are named. The motivation is to avoid a naming collision problem found by Daniel. Before this commit, we were getting an error on the following file tests/lean/run/collision_bug.lean. Now, transitive instances contain the prefix "_trans_". It makes it clear this is an internal definition and it should not be used by users. This change also demonstrates (again) how the `rewrite` tactic is fragile. The problem is that the matching procedure used by it has very little support for solving matching constraints that involving type class instances. Eventually, we will need to reimplement `rewrite` using the new unification procedure used in blast. In the meantime, the workaround is to use `krewrite` (as usual).
2016-02-04 13:15:42 -08:00
@gt.{1} nat nat._trans_of_decidable_linear_ordered_semiring_13 x
(@zero.{1} nat nat._trans_of_decidable_linear_ordered_semiring_6))
S :
set.{1} nat
chore(tests): mass-update for pp.binder_types false
2016-05-31 22:14:42 -04:00
@finset.sep.{1} nat (λ a b, nat.has_decidable_eq a b)
(λ x,
fix(library/tc_multigraph): avoid name collisions @avigad, @fpvandoorn, @rlewis1988, @dselsam I changed how transitive instances are named. The motivation is to avoid a naming collision problem found by Daniel. Before this commit, we were getting an error on the following file tests/lean/run/collision_bug.lean. Now, transitive instances contain the prefix "_trans_". It makes it clear this is an internal definition and it should not be used by users. This change also demonstrates (again) how the `rewrite` tactic is fragile. The problem is that the matching procedure used by it has very little support for solving matching constraints that involving type class instances. Eventually, we will need to reimplement `rewrite` using the new unification procedure used in blast. In the meantime, the workaround is to use `krewrite` (as usual).
2016-02-04 13:15:42 -08:00
@gt.{1} nat nat._trans_of_decidable_linear_ordered_semiring_13 x
(@zero.{1} nat nat._trans_of_decidable_linear_ordered_semiring_6))
chore(tests): mass-update for pp.binder_types false
2016-05-31 22:14:42 -04:00
(λ a, nat.decidable_lt (@zero.{1} nat nat._trans_of_decidable_linear_ordered_semiring_6) a)
feat(frontends/lean): allow user to overload notation containing foldr/foldl and/or scoped expressions see new tests for a summary of new features see issue #800
2015-08-16 18:21:29 -07:00
s :
finset.{1} nat
Reference in a new issue Copy permalink