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
This would be very useful for one of the projects I maintain although for a different purpose compared to the typical Mima one. In my specific case I would want to report the bytecode diff for specific classes/modules to see if there are any potential performance impacts for critical sections of the code and having this exposed via sbt plugin would help in greatly trivialize the problem.
@retronym Would you be interested in looking into this if I helped revived the PR at #52 (it seems to be dead?). Also pinging @SethTisue since you were trying to get that PR over the finish line.
On Mon, 3 Jul 2023 at 08:34, Matthew de Detrich ***@***.***> wrote:
This would be very useful for one of the projects I maintain although for
a different purpose compared to the typical Mima one. In my specific case I
would want to report the bytecode diff for specific classes/modules to see
if there are any potential performance impacts for critical sections of the
code and having this exposed via sbt plugin would help in greatly
trivialize the problem.
@retronym <https://github.com/retronym> Would you be interested in
looking into this if I helped revived the PR at #52
<#52> (it seems to be
dead?). Also pinging @SethTisue <https://github.com/SethTisue> since you
were trying to get that PR over the finish line.
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAQAD2GW37UHMSYN27MCX3XOHZPHANCNFSM4DN6FLXQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
Add a convenient way for SBT users to compare the current results of
package
to a specified reference version, in the same way as MiMa.The text was updated successfully, but these errors were encountered: