rmeta • Lines: 189rust
#rustc 1.92.0 (ded5c06cf 2025-12-08)��١� �T�6 a��D�
-5080178c80bf7a93� profiling_procmacros�e�9���H�A����
� -0d8c0e1df4c15e00� �* *�٭T��HО�9� -3e2e950d4bac10b5�� puffin�4� �<� profile-with-puffin��� �� puffin_impl�\� �<� ��� �� optick�4� �<� profile-with-optick��� �� optick_impl�\� �<� ��� �� superluminal_perf��� �<� profile-with-superluminal��� ��% superluminal_impl��� �<� �ܞ ��% tracing�<� �<� profile-with-tracing��� �� tracing_impl�d� �<� ��� �� tracy_client�d� �<� profile-with-tracy��� ��
tracy_impl�T� �<� ��� �� type_check_impl�|� �<�
type-check�d� �� �
empty_impl� scope� function_scope� register_thread� finish_frame� �
all_functions�l� function�D� �$� �,� �t� �|� �d�
��� �� �� �� �� �� �� � �}
��# �� �Ԓ �t� T� �� � Opens a scope. Two variants:� �!H E - profiling::scope!(name: &str) - Opens a scope with the given name� �ja ^ - profiling::scope!(name: &str, data: &str) - Opens a scope with the given name and an extra� ��b _ datafield. Details of this depend on the API, but it should be a &str. If the extra data is� ��e b named, it will be named "tag". Some APIs support adding more data (for example, `optic::tag!`)� �� <� ```� �� profiling::scope!("outer");� �� for _ in 0..10 {� ��E B profiling::scope!("inner", format!("iteration {}").as_str());� ,� }� <��
'|� e � � � � , � 8�
$� & � 8� $� *� � � % � � � , � 8�
$� & � 8� $� $ � , � 8 data� $� & � 8� $� *� � � % � �� ��A > Opens a scope automatically named after the current function.� ��Q N - profiling::function_scope!() - Opens a scope with the current function name� ��t q - profiling::function_scope!(data: &str) - Opens a scope with the current function name and an extra data field.� �� <��
�� fn function_a(){� ��% " profiling::function_scope!();� ,�� ��" fn function_b(iteration: u32){� ��P M profiling::function_scope!(format!("iteration {}", iteration).as_str());� ,�� <��
'|� � � � � � *� � � % � � � , � 8� $� & � 8� $� *� � � % � �� �� _ \ Registers a thread with the profiler API(s). This is usually setting a name for the thread.� ��
Two variants:� ��
[ X - register_thread!() - Tries to get the name of the thread, or an ID if no name is set� �� O L - register_thread!(name: &str) - Registers the thread using the given name� '|� � � � � � *� � � % � � � , � 8�
$� & � 8� $� *� � � % � ��
�� a ^ Finishes the frame. This isn't strictly necessary for some kinds of applications but a pretty� ��
# normal thing to track in games.� '|�
�
�
�
�
*�
�
�
% �
T� ac�YE�(p� ��q����1��1������Ӈ������Z2+"/�=����F�q<H���>�1�y}o�Ѻ~�ِ��Z��7��q��[��� � �
�
� � )))) �?E
2
��������
� e
� ����<B
/
� -9Ndw @F
3
" %� ac�YE�(��Z�`*� �������ODHT �� 1�y}o�� �~�ِ�� Z��7��q
������� ����F�q Z2+"/�= p� ��q ac�YE�( <H���>� ��[��� ����1�� 1������� h
8�D8� ?~L��wih
8�D8� ?~L��wi ]/home/palash/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/profiling-1.0.17/src/lib.rs� ���hσ�6|U>4;�{ � �b;a Q %
&
. %
&
-`N (6 %
&
. %
&
$((((((... )))''' %%+&$%%+&$ �@�k��{c�8ĩ.� d/home/palash/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/profiling-1.0.17/src/empty_impl.rs� w>�C(1�Ѹ���DŽk� �
4!Ibcf F$BRu&#Q `\P b$ ��� [ӊ
���/�(�� �7 x86_64-unknown-linux-gnu�Pb�_x� ��
�)��� profiling� -bceb494ff0df8665�ac�YE�( �# � � ` ! N� rust-end-file