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
It would be helpful to have a setup that allows to benchmark compilation times. This would allow to observe the effect changes to the derivation mechanism may have on the compilation time (of derivation of typeclasses).
Futhermore, one would probably need to have one or more reference projects with a sufficient amount of derivation (maybe even one for each typeclass (Arbitrary, Cogen, Shrink)). Using the test code of this project might be problematic as it will change over time (while the reference project should ideally remain unchanged).
The text was updated successfully, but these errors were encountered:
It would be helpful to have a setup that allows to benchmark compilation times. This would allow to observe the effect changes to the derivation mechanism may have on the compilation time (of derivation of typeclasses).
This blog post might be a good start: https://www.scala-lang.org/blog/2018/06/04/scalac-profiling.html - or maybe there are other sources?
Futhermore, one would probably need to have one or more reference projects with a sufficient amount of derivation (maybe even one for each typeclass (
Arbitrary
,Cogen
,Shrink
)). Using the test code of this project might be problematic as it will change over time (while the reference project should ideally remain unchanged).The text was updated successfully, but these errors were encountered: