Leonardo de Moura efabd2280c feat(library/unifier): allow unifier to unfold opaque definitions of the current module ... It is not clear whether this is a good idea or not. In some cases, it seems to do more harm than good. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com>		2014-07-05 00:46:03 -07:00
..
bit.lean	feat(library/unifier): allow unifier to unfold opaque definitions of the current module	2014-07-05 00:46:03 -07:00
classical.lean	feat(library/standard): add 'classical' module	2014-07-04 22:50:30 -07:00
funext.lean	feat(library/standard): add function extensionality axiom	2014-06-30 11:53:04 -07:00
logic.lean	feat(library/unifier): allow unifier to unfold opaque definitions of the current module	2014-07-05 00:46:03 -07:00
Makefile	feat(build): add Makefile for libraries	2014-06-28 18:41:53 -07:00
num.lean	feat(frontends/lean): add 'class' and 'instances' infrastructure	2014-07-04 14:28:09 -07:00
option.lean	feat(frontends/lean): add 'class' and 'instances' infrastructure	2014-07-04 14:28:09 -07:00
pair.lean	feat(frontends/lean/elaborator): add class instance elaboration	2014-07-04 15:45:50 -07:00
standard.lean	feat(library/standard): add pairs	2014-07-03 20:43:16 -07:00
string.lean	feat(frontends/lean): add 'class' and 'instances' infrastructure	2014-07-04 14:28:09 -07:00
tactic.lean	fix(library/standard): orelse notation, avoid conflict with inductive datatype declaration	2014-07-04 10:10:05 -07:00
unit.lean	feat(frontends/lean): add 'class' and 'instances' infrastructure	2014-07-04 14:28:09 -07:00