askama - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	parser: add type for `Node::Match`	René Kijewski	2023-08-01	1	-1/+1
\|
*	parser: add type for `Node::Call`	René Kijewski	2023-08-01	1	-1/+3
\|
*	parser: add type for `Node::Import`	René Kijewski	2023-08-01	1	-1/+1
\|
*	parser: add `Ast::nodes()` method	René Kijewski	2023-08-01	1	-0/+4
\|
*	parser: impement `PartialEq` for `Ast`	René Kijewski	2023-08-01	1	-0/+7
\|
*	parser: implement `Debug` for `Parsed`	René Kijewski	2023-08-01	1	-1/+9
\|
*	parser: use `?`	René Kijewski	2023-08-01	1	-5/+1
\|
*	parser: ensure correct drop order for `Parsed`	René Kijewski	2023-08-01	1	-2/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	According to [RFC 1857] the fields of a struct are dropped in the same order as they are declared. For `struct S { a: A, b: B }` field `a` is dropped before field `b`. Our struct `Parsed` is self referencial. Its field `ast` depends on `source`, so `source` must outlife `ast`. This PR changes the order of the fields to reflect this requirement. In practice it should not matter, because we know that the variant of `Node` won't access the string data during their `Drop`, but better safe than sorry - maybe `Node` changes in the future. [RFC 1857]: https://rust-lang.github.io/rfcs/1857-stabilize-drop-order.html
*	parser: move node parsers into impl block	Dirkjan Ochtman	2023-07-31	1	-22/+2
\|
*	parser: simplify top-level parser match	Dirkjan Ochtman	2023-07-31	1	-29/+24
\|
*	parser: add top-level Ast type	Dirkjan Ochtman	2023-07-31	1	-33/+40
\|
*	parser: move nested_parenthesis() helper into node module	Dirkjan Ochtman	2023-07-31	1	-48/+0
\|
*	parser: move helper functions into State impl	Dirkjan Ochtman	2023-07-31	1	-61/+61
\|
*	parser: move trait impl closer to type definition	Dirkjan Ochtman	2023-07-31	1	-11/+0
\|
*	parser: move single-use functions into caller	Dirkjan Ochtman	2023-07-31	1	-13/+13
\|
*	Extract askama_parser crate	Dirkjan Ochtman	2023-07-31	1	-0/+384