-
Notifications
You must be signed in to change notification settings - Fork 161
is changing Array
-> FrozenArray
binary compatible?
#789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Array
-> FrozenArray
binary compatible?
Yes, see: Specifically:
|
Right, this does make sense in the context of js+dom :) Thanks! Are there extension methods for the frozen array somewhere? (To get the .contains back, for example) |
I guess not, sorry about that 😕 we should add them, or find some other solution. |
No worries! (there are always workarounds to be found :) ) |
After updating
2.3.0
->2.6.0
(as part of Laminar update) I got a compilation error in this piece of code:Option(ev.dataTransfer).exists(_.types.contains(format))
types
became aFrozenArray
and no longer has the.contains
method.So this is obviously not source-compatible (which is okay and expected), but is it binary compatible?
PR:
#763
Relevant change:
976316c#diff-bee8c85a4317c93e362f64be85e566c7583875855b80a078cc8dddc277700a72R78
The text was updated successfully, but these errors were encountered: