Go to file
Wolfgang Bumiller 080f62916e macro: errors shouldn't discard the code
Otherwise we'll get even more errors.
Consider this example:

    #[api(...)]
    struct Foo { ... }
    impl MyTrait for Foo { ... }

If the #[api] macro fails and does not at least produce the
`struct Foo{}` along with its `compile_error!()` output,
then in addition to our macro errors, we'll see errors about
trying to implement `MyTrait` for an unknown thing called
`Foo`.

Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-08-08 14:04:28 +02:00
api-test macro: derive ser/de for newtypes just like structs 2019-08-08 11:29:12 +02:00
proxmox cleanup Cargo.toml files 2019-08-05 14:09:54 +02:00
proxmox-api formatting fixup 2019-08-05 09:45:14 +02:00
proxmox-api-macro macro: errors shouldn't discard the code 2019-08-08 14:04:28 +02:00
proxmox-sys formatting fixup 2019-08-05 14:14:23 +02:00
proxmox-tools formatting fixup 2019-08-05 14:14:23 +02:00
.gitignore initial import, starting with vec & io helpers 2019-06-06 14:00:25 +02:00
Cargo.toml add an api-test module 2019-06-12 15:54:52 +02:00
Makefile add make apitest 2019-06-18 17:53:43 +02:00
rust-toolchain initial import, starting with vec & io helpers 2019-06-06 14:00:25 +02:00
rustfmt.toml initial import, starting with vec & io helpers 2019-06-06 14:00:25 +02:00