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
Constraint check failure for areSame.T
Int should be massive.munit._Assert.RefType
Int should be haxe.extern.EitherType<{ }, haxe.Function>
This makes sense when looking at RefType, which requires the parameters to be either a structure or a function. RefType was added in #144 by @SlavaRa. This behavior is probably expected and these calls can easily just be replaced with areEqual(). However, this should probably be clarified in the method's docs? The description of the two methods is almost identical:
Assert that two values are not equal
vs
Assert that two values are one and the same
with no mention of what "values" means exactly (more specifically that not all values are allowed for areSame()).
The text was updated successfully, but these errors were encountered:
Gama11
added a commit
to HaxeFlixel/flixel
that referenced
this issue
Mar 17, 2018
Flixel's CI broke with the 2.2.1 release of MUnit. It seems
areSame()
no longer supports basic types such asInt
,Float
orBool
:This makes sense when looking at
RefType
, which requires the parameters to be either a structure or a function.RefType
was added in #144 by @SlavaRa. This behavior is probably expected and these calls can easily just be replaced withareEqual()
. However, this should probably be clarified in the method's docs? The description of the two methods is almost identical:vs
with no mention of what "values" means exactly (more specifically that not all values are allowed for
areSame()
).The text was updated successfully, but these errors were encountered: