Exporting app description during compliation for tracing purposes? about rfcs HOT 2 OPEN

The above pitfall is probably not of concern: RTIC already operates with nested macros in mind.

Another question entirely regards additional metadata. Of high interest to my thesis is the monitoring of shared resources (both value and lock status), but also that of queue sizes. For resources values the in-memory address must be known. Must this address be found after building by help of build.rs?

from rfcs.

RTIC parses the app and will see the attributes at top level. RTIC does currently NOT parse the function bodies and will not see the inner attributes. In both cases the attributes will be remained and the corresponding expansions performed. As far as I know we cannot control the order of macro expansion, so it might be that the #[trace] have already been expanded at the point where RTIC gets the token stream (this I'm not 100% sure of however). In any case to ensure that RTIC includes the #[trace] in an intelligent way I believe it needs to be part of the RTIC syntax (on par with other attributes that RTIC handles). In that case it could as well be part of the #[task] attributes. Its certainly doable and not high effort, but as everything else it adds to the complexity and I'm not sure such a change would be accepted.

from rfcs.