Leonardo de Moura 182812a278 chore(library/init/lean/parser/token): make sure generate code does contain partially applied reader_t.or_else and reader_t.bind ... @kha This one was crazy, the compiler created a join point for the continuation of the match-expression. Each case of the match was invoking the join point with a different parser. Two of the branches were the partially applied `reader_t.bind` and `reader_t.orelse`. This change did not improve the performance much, but it makes sure we don't waste time trying to figure out why we have these two partial applications in the call graph.		2018-11-08 17:39:46 -08:00
..
init	chore(library/init/lean/parser/token): make sure generate code does contain partially applied reader_t.or_else and reader_t.bind	2018-11-08 17:39:46 -08:00
leanpkg.path	feat(leanpkg): add package manager	2017-05-01 14:11:38 -07:00
library.md	chore(library/library.md): update documentation	2017-08-16 14:17:26 -07:00
Makefile.in	chore(library/Makefile.in): suppress comment output	2018-11-05 17:15:01 +01:00
relative.py	feat(library,src/CMakeLists): use simple Makefile by Simon Hudon to bring back some degree of parallel compilation	2018-10-19 09:52:01 +02:00