CI

[4meta5]

Ideally CI would verify that the macros output valid Rust code. Compiling the crate itself is not as helpful because it does not tell us if the macro expansion is valid Rust.

Note that this ideal may first require #8 because most of our macro output isn't valid Rust until deps include all that are required.

[ggonzalez94]

@4meta5 we could add a step that expands the macros(but I think we will need tests or examples for this to be useful)

- name: Expand macros
      run: cargo expand 

Aditionally we could trybuild for testing
WDYT?

[ggonzalez94]

I created #18 since I wasn't sure what to add for verifying the macro itself, but if we are happy with this we can close the issues with #19

[ggonzalez94]

Marking this as closed in favor of #18. If we find things we need to add specific to macros we can come back and reopen this.