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
Revert "[dart2wasm] Don't dartify JS values when returning as void"
This reverts commit 4bb05dc.
Reason for revert: suspected to be blocking rolls into Flutter, e.g. flutter/flutter#166618
Original change's description:
> [dart2wasm] Don't dartify JS values when returning as void
>
> When calling a JS function that returns `void`, avoid dartifying the
> result.
>
> Technically the return value of `void` functions can still be used, by
> casting the return type to `Object?` or `dynamic`. However this
> shouldn't be done, and `dartifyRaw` overhead just to support this case
> which should be extremely rare is too much.
>
> Any hacky code that uses return values of `void`-returning JS interop
> functions can manually dartify the retrun values with `toDart` or
> similar.
>
> Issue: #60357
> Change-Id: Ic370c7cf6eb6982f61f8a07c91e3bb93c5345ac6
> Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/417240
> Reviewed-by: Srujan Gaddam <[email protected]>
> Reviewed-by: Martin Kustermann <[email protected]>
> Commit-Queue: Ömer Ağacan <[email protected]>
Issue: #60357
Change-Id: I27e0a7355eeee94d1dc02fba0c9569b53954d1c5
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/420780
Bot-Commit: Rubber Stamper <[email protected]>
Reviewed-by: Ömer Ağacan <[email protected]>
Reviewed-by: Srujan Gaddam <[email protected]>
Commit-Queue: Derek Xu <[email protected]>
0 commit comments