Leonardo de Moura 0dcdc2c198 feat(library/init/lean/parser/term): add support for "named" patterns n@(x :: s) ... @kha, the implementation is a little bit hackish. It is whitespace sensitive to avoid `f @g`, an application with argument `@g` to be parsed as a named pattern. Here are other approaches I have considered: 1- In the `namedPattern`, we add a guard that ensures the pattern is *not* an identifier. Thus, `f @g` would not be considered a valid `namedPattern`. Drawback: we would always try to parse it as a namedPattern first, fail, and then try as an application. 2- Enforce whitespace before application arguments. Drawback: `f(a+b)` would not be a valid application anymore.		2019-07-16 10:09:01 -07:00
..
init	feat(library/init/lean/parser/term): add support for "named" patterns n@(x :: s)	2019-07-16 10:09:01 -07: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	fix(library/Makefile): recreate libleanstdlib.a from scratch to avoid conflicts when moving files	2019-05-08 18:13:17 +02:00
relative.py	fix(library/relative): lean --path returns Windows filenames, but make expects Unix ones	2019-07-05 11:24:15 +02:00