Folkert de Vries

That means that for now we should disallow it on function prototypes, right? E.g. `inline` currently behaves like that: ``` warning: `#[inline]` is ignored on function prototypes --> src/main.rs:2:5 |...

> I realized that this RFC currently fails to specify how `#[align(…)]` interacts with `#[track_caller]`. Unfortunately, it seems that `#[track_caller]` has problems ([rust-lang/rust#143162](https://github.com/rust-lang/rust/issues/143162)) that probably need to be resolved before...

I have `static_align` ready to go here https://github.com/rust-lang/rust/compare/master...folkertdev:rust:static-align, should I wait for the RFC to be re-approved, or can that be merged already. Based on discussion so far everyone seemed...

Looks like you need to update your CI to use a newer ubuntu version (we usually use `ubuntu-latest`, but maybe there is a reason you pin a specific version?) >...

Ok well maybe `22.04` still works, or maybe latest got updated with a fix? (I can try that too) I'm also not sure what's up with the azure runners, but...

ah, I'll split that out then. I'd just like CI to check my work, not everything runs locally.

I misinterpreted what C actually does earlier. The usage of ```c int foo[] = { 0 } ``` is [extremely widespread](https://github.com/search?q=%22%5D+%3D+%7B+0+%7D%22++language%3AC&type=code), but at least with modern compilers it is equivalent...

Well I was playing with more complicated zero initializers (e.g. `struct {short; int y;} arr6[4] = { 0 };`, but I don't really know enough about C (or C++, and...

Btw, wouldn't something like `cargo insta` (or some other snapshot testing solution) be really useful for testing the output of `c2rust-transpile`? I've basically been doing that manually. Unless I'm missing...

Yes this looks good, thanks!