parser/ast as separate library

[cemoktra]

Description
I wanted to play around with typical and evetually integrating it into tonic. For this purpose it would be convenient to have schema parsing as a library.

Alternatives considered
I coul dtake inspiration and rewrite parsing, but it exists ;)

[stepchowfun]

Integrating into tonic seems worthwhile! But I'm not sure what it would take exactly. Does tonic allow prost to be swapped with something else?

BTW, if you want to prototype it, the parser is in parser.rs. This is the entrypoint:

typical/src/parser.rs

Lines 195 to 199 in fbef90e

	pub fn parse(
	source_path: &Path,
	source_contents: &str,
	tokens: &[token::Token],
	) -> Result<schema::Schema, Vec<Error>> {

[cemoktra]

tonic recently pushed out all prost related code into two crates that implement some traits. so that should be quite easy.

https://github.com/hyperium/tonic/tree/master/tonic-prost
https://github.com/hyperium/tonic/tree/master/tonic-prost-build

one crate handles message (and service; which i could hard code for tests) generation, and the other crate implements a "codec" and defines how messages are de-/serialized