Yuya Nishihara 0c05c541a1 fileset, templater: insert intermediate InvalidArguments error type ... This will help extract common FunctionCallNode<'i, T> type. We don't need freedom of arbitrary error type choices, but implementing From<_> is the easiest option I can think of. Another option is to constrain error type by the expression type T through "T::ParseError: ArgumentsParseError" or something, but it seemed a bit weird that we have to use trait just for that.		2024-05-23 10:18:36 +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: explicitly indicate paths to publish	2024-04-15 20:37:00 -07:00
src	fileset, templater: insert intermediate InvalidArguments error type	2024-05-23 10:18:36 +09:00
tests	tree_builder: propagate errors from write_tree()	2024-05-22 06:46:38 -07:00
testutils	tree_builder: propagate errors from write_tree()	2024-05-22 06:46:38 -07:00
Cargo.toml	cargo: explicitly indicate paths to publish	2024-04-15 20:37:00 -07:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00