Sam Johnson

> @sam0x17 any advice on how we may be able to fix this? This is likely some item in the expansion of `dev_mode` that does not come with built-in doc...

So glancing through the dev mode implementation I didn't catch any undocumented items slipping through. Could you open the docs on the item it is complaining about @sacha-l and see...

> Looking forward to see more aspects of the execution part coming out. Any initial design, thoughts or similar? @kianenigma Right now I am working on the system pallet `do_work`...

now need to have `Task` aggregate like Call/Event/etc does

FYI I implemented a scheme very similar to this in my [macro_state](https://crates.io/crates/macro_state) crate. So far it seems to avoid most of the pitfalls. If not, pull requests welcome!

> You need to throw away the state every time and make sure state for different crates isn't mixed In my experience, having a build number that increments with every...

btw a much cleaner way of doing this is with the outer macro pattern

so to be clear, an example of the outer macro pattern would be: ```rust #[my_outer_attribute] mod my_mod { #[attribute_1] pub fn some_fn() { #[attribute_2] let some_expr = 33; } #[attribute_1]...

@aikixd the standard way of doing this (especially for things like URL handler attributes, which is one I've specifically implemented this way before) is to use the outer macro pattern....

Another more exotic way you can do this is using the `macro_magic` token teleportation trick (which is completely legal in stable rust and doesn't violate the pure-functionness of proc macros),...