Jakob Hellermann

The labels are currently generated with `contraint=false`, which leads to the problem. Without it, the labels are more readable, but the diagram as a whole isn't  Different colors definitely...

There are two aspects of systems that define whether two of them can run in parallel. The first one is explicit `after`/`before` conditions, that is what's currently being visualized and...

The information is definitely there, `bevy_mod_debugdump` already displays tooltips showing which components and resources are accessed. You can then need to call [Access::is_compatible](https://docs.rs/bevy_ecs/0.6.1/bevy_ecs/query/struct.Access.html#method.is_compatible) to check whether systems can be run...

Broken in which way? The only problem I noticed is that they don't disable the `LogPlugin` like the examples do, so you can't do `cargo run | dot -Tsvg` directly,...

I don't think so. I pasted them in a new file and everything worked as expected. What error message are you getting?

sure, that would be nice

Actually, I think a tweak in the macro will probably not be enough. Since `cargo watt` patches syn to use `proc_macro2` instead of `proc_macro`, other crates (like proc_macro_error) are likely...

I don't think it is possible to make any approach work flawlessly for every crate, at least not without `wasm`-macros being implemented as first-class citizens in rustc. So I think...

I didn't know about `proc_macro::bridge`. Where can I find documentation about it?

I wonder whether this could be used in `watt` directly? If watt could handle `pub extern "C" fn the_macro(input: proc_macro::TokenStream) -> proc_macro::TokenStream` (not proc_macro2), then the translation from regular macro...