Skip to content

Conversation

smarter
Copy link
Member

@smarter smarter commented Jul 8, 2025

Previously we only profiled macro expansion, but even non-macro inline calls can have a significant impact on performance (e.g. if we're doing typeclass derivation) and are worth tracking. This does not seem to significantly impact the size of traces in practice.

Previously we only profiled macro expansion, but even non-macro inline calls can
have a significant impact on performance (e.g. if we're doing typeclass
derivation) and are worth tracking. This does not seem to significantly impact
the size of traces in practice.
@WojciechMazur WojciechMazur merged commit 8a14de3 into scala:main Jul 8, 2025
29 checks passed
tgodzik pushed a commit to scala/scala3-lts that referenced this pull request Jul 23, 2025
Previously we only profiled macro expansion, but even non-macro inline
calls can have a significant impact on performance (e.g. if we're doing
typeclass derivation) and are worth tracking. This does not seem to
significantly impact the size of traces in practice.
[Cherry-picked 8a14de3]
tgodzik pushed a commit to scala/scala3-lts that referenced this pull request Jul 24, 2025
Previously we only profiled macro expansion, but even non-macro inline
calls can have a significant impact on performance (e.g. if we're doing
typeclass derivation) and are worth tracking. This does not seem to
significantly impact the size of traces in practice.
[Cherry-picked 8a14de3]
@WojciechMazur WojciechMazur added this to the 3.7.3 milestone Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants