You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it will be more idiomatic to mark the profiling function like this
#[profile_fn]fnfn_name<T>(param:T){// If a function is complex, profile a section.#[profile_section]{// Optional: manually drop.// Section automatically drops when going out of scope.drop(inner);}}
This API looks like the profiling crate, and it looks more ergonomic to me.
The text was updated successfully, but these errors were encountered:
I agree that appears less verbose, and is especially nice in that the function signature need not be duplicated. IDE support for macros can be hit or miss though. Also, sometimes compile times can be negatively affected. So, it's not a clear win. We could provide it as an option though.
I think it will be more idiomatic to mark the profiling function like this
This API looks like the profiling crate, and it looks more ergonomic to me.
The text was updated successfully, but these errors were encountered: