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
The problem seem to exits for int underlyings but not string ones (As is tested in the existing unit tests). Code generation for value types might be broken.
The bug affected all classes that don't have an == or != operator and `int``doesn't.
Make me think that for intrictic types (int, long, ...) we should still use the operator even if it isn't user-defined. I'll create an issue for that too.
Seen by @julienadam in internal code, need to investigate.
The text was updated successfully, but these errors were encountered: