Remove 'static requirement on run#3006
Conversation
|
I think the macOS backend is currently unsound if Though that should be fixable. Re if the backend doesn't ever return, then not having |
|
@madsmtm the thing is that we return, but the @daxpedda I think I've missed something? Because it seems like other code is bound to @madsmtm I was mostly curios about ios. |
|
This should work fine for Web.
I can fix that. |
madsmtm
left a comment
There was a problem hiding this comment.
I'm not sure I understand you, but I was trying to say that the change should be sound on iOS (even though it doesn't compile as-is).
Required an |
Yeah, that's what I was afraid of, so I left it as is, unless a backend maintainer approves. |
|
@madsmtm you've replied about macOS initially though, not ios though. I guess your reply about ios was indirect though. Does it matter for macOS how you cleanup, if you basically drop the |
|
I guess I'll do the beta 2 with it like that, and then we could probably gather some feedback whether we'd really need it to keep that way. |
c8e1bac to
1b9af6a
Compare
There's no need to force the static on the users, given that internally some backends were not using static in the first place.
1b9af6a to
6b3ead1
Compare
There's no need to force the static on the users, given that internally some backends were not using static in the first place.
CHANGELOG.mdif knowledge of this change could be valuable to users