4 Commits (71b6cc4d1783b0e7b5a22a5a16fc9bdbde0a62fd)

Author	SHA1	Message	Date
Pascal Kuthe	90348b889f	revamped snippet text element parsing ... Snippet text elements can contain escape sequences that must be treated properly. Furthermore snippets must always escape certain characters (like `}` or `\`). The function has been updated to account for that. `text` is now also included with `anything` to match the grammar and can also match empty text. To avoid infinite loops the `non-empty` combinator has been added which is automatically used in the `one_or_more` and `zero_or more` combinator where the problemn would occur.	2 years ago
Urgau	3f90dafa3c	Remove now unused the pattern combinator	2 years ago
Urgau	e973b71c83	Optimize LSP snippet parsing	2 years ago
Michael Davis	c8e6857aff	Add a parser-combinator crate ... Parser-combinators are one of the simpler tools for building ad-hoc parsers. They're a good fit because they are... * Small: each parser / parser-combinator is around 10 LOC. * Functional: helix_core strives to be a functional set of utilities usable throughout the rest of the editor. * Flexible: use them to build any sort of ad-hoc parser. In the child commit, we'll parse LSP Snippet syntax using these new parser combinators. Why not use an existing parser-combinator crate? Existing popular parser-combinator crates have histories of making breaking changes (for example nom and combine). > Implementation note: I tried to not introduce a new trait since the > types can be expressed in terms of `impl Fn`s. The trait is necessary > to build `seq` implementations without a proc macro though, and also > allows us to use `&'static str`s very conveniently: see the trait > implementation for `&'static str`.	2 years ago