helix-ext - [contrib] fork of the helix editor, with various inactive and rejected patches applied

	Commit message (Collapse)	Author	Age
*	use workspace inheritance for common version (#8925)	Skyler Hawthorne	2023-12-05
\|
*	set Cargo feature resolver to v2 (#8917)	Fomalhaut Weisszwerg	2023-11-27
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* fix: version of Cargo feature resolver. This commit solve the ambiguity to determin the version of resolver. To get more detail, see the following two documents: - https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions - https://doc.rust-lang.org/edition-guide/rust-2021/default-cargo-resolver.html * unified: Rust edition in all workspaces. Now, the Rust 2021 is available in all workspaces. * fined up: Cargo.toml by using workspace inheritance. To get more detail of the `workspace.package` table, see a following document: - https://doc.rust-lang.org/cargo/reference/workspaces.html#the-package-table
*	Remove now unused the pattern combinator	Urgau	2023-03-08
\|
*	Add a parser-combinator crate	Michael Davis	2023-03-08
	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`.