v0x0g

Had this issue happen to me as well, with the following (on `rustfmt 1.7.1-nightly (fda509e 2024-06-25)`): ```rust macro_rules! my_macro { () => { // Breaks #[doc(concat!( "Multi\ Line" ))] pub...

Hey @xNxExOx I'd be willing to give you a hand with debugging this one if you don't telling me what you need. It would also be helpful to have the...

This seems like an interesting issue (also your sampling profiler sounds very cool). I'm a bit confused on the exact order of these locks and accesses - I'm not familiar...

I'm not sure what you mean by this - you can already profile custom scopes with the example code you gave, using `puffin::profile_scope!("name");`. I'm guessing you would like to be...

> Returning a value from a macro isn't a hygiene issue, so I feel like this should be possible? Yeah it is unfortunately, that's why I had to do my...

That's my point, sadly it doesn't work, because of macro hygiene. The identifier `_profiler_scope` declared inside the macro has a different scope than the identifier `_profiler_scope` that you try to...

Oh yeah that works too! This should be what you want then: ```rust #[macro_export] macro_rules! profile_scope_custom { ($name:expr) => { $crate::profile_scope_custom!($name, "") }; ($name:expr, $data:expr) => { if $crate::are_scopes_on() {...

@chrisduerr I have made #213 for you We'll have to wait for one of the maintainers to merge it. Until then you can use [my fork](https://github.com/v0x0g/puffin/tree/feature/puffin_extend_profile_scopes_macro) or just copy the...