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 came across this today when trying to update some stuff in the Dotty Community build and realized that munit when synced was actually failing in the community build. The error that it's failing with is the same that you see in #545 where the expected message for the @implicitNotFound on the Compare trait is no longer showing and instead you just get:
missing argument for parameter compare of method assertEquals in trait Assertions: (implicit loc: munit.Location, compare: munit.Compare[None.type, Some[Int]])
Looking at the commits between 3.1.2 and 3.1.3 it wasn't clear what was causing this, and I didn't try and bisect it yet.
Also adding that when I try to minimally reproduce this same scenario with 3.1.2 and 3.1.3 in a hello world project that is using @implicitNotFound, both work fine. So it's something more involved here. Also looking more closely I think this might be a red herring and something else is going wrong here before it even needs to look for the @implicitNotFound message.
Actually in a minimal test I can reproduce this using 3.1.3 with:
I came across this today when trying to update some stuff in the Dotty Community build and realized that
munit
when synced was actually failing in the community build. The error that it's failing with is the same that you see in #545 where the expected message for the@implicitNotFound
on theCompare
trait is no longer showing and instead you just get:Looking at the commits between 3.1.2 and 3.1.3 it wasn't clear what was causing this, and I didn't try and bisect it yet.
You can see the same failures in a pr in Dotty here: https://github.com/lampepfl/dotty/runs/7481846884?check_suite_focus=true
The text was updated successfully, but these errors were encountered: