lean2/tests/lean/binder_overload.lean.expected.out

{x ∈ S | x > 0} : set ℕ
{x ∈ s | x > 0} : finset ℕ
@set.sep.{1} nat
  (λ x,
     @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
@finset.sep.{1} nat (λ a b, nat.has_decidable_eq a b)
  (λ x,
     @gt.{1} nat nat._trans_of_decidable_linear_ordered_semiring_13 x
       (@zero.{1} nat nat._trans_of_decidable_linear_ordered_semiring_6))
  (λ a, nat.decidable_lt (@zero.{1} nat nat._trans_of_decidable_linear_ordered_semiring_6) a)
  s :
  finset.{1} nat
-												chore(tests): mass-update for pp.binder_types false

											
										
										
											2016-06-01 02:14:42 +00: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 21:15:42 +00:00
+								@set.sep.{1} nat
-												chore(tests): mass-update for pp.binder_types false

											
										
										
											2016-06-01 02:14:42 +00: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 21:15:42 +00: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-06-01 02:14:42 +00: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 21:15:42 +00: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-06-01 02:14:42 +00: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-17 01:21:29 +00:00
+								  s :
 								  finset.{1} nat