Yuya Nishihara 3e029537c6 fileset: add basic AST-level object and matcher builder ... FilesetExpression is similar to RevsetExpression, but there are two major differences: - Union is represented as N-ary operator, - Expression node isn't Rc-ed. The former is because of the nature of the runtime Matcher objects. It's easier to construct a Matcher from flattened union expressions than from a binary tree. The latter choice comes from UnionAll(Vec<FilesetExpression>), which doesn't have to be Vec<Rc<FilesetExpression>>, and Rc<[FilesetExpression]> can't be constructed from [Rc<_>, ..]. Anyway, the internal representation may change as needed. Another design decision I made is Vec<Pattern(RepoPathBuf)> vs Pattern(Vec<RepoPathBuf>). I chose the former because it will be more closer to the parsed tree of the fileset language.		2024-04-06 23:59:54 +09:00
..
benches
gen-protos	Use { workspace = true } to appease VS Code's Cargo.toml parser	2023-08-22 21:38:53 -07:00
proc-macros	cargo: mark the jj-lib-proc-macros crate for publish	2024-03-06 20:35:38 -08:00
src	fileset: add basic AST-level object and matcher builder	2024-04-06 23:59:54 +09:00
tests	revset: add working_copies() function	2024-04-01 19:36:53 -06:00
testutils	compile integration tests as a single binary	2024-02-06 18:19:41 -08:00
Cargo.toml	test_conflicts and test_resolve_command: use indoc! to indent conflict markers in tests	2024-03-22 23:27:25 -07:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00