-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Clean up the bindings APIs #86438
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
Clean up the bindings APIs #86438
Conversation
|
cc @goderbauer for review Gardeners: In case this causes any devicelab failures, please do not hesitate to revert it. Thanks! |
goderbauer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a unit test to cover this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
|
This pull request is not suitable for automatic merging in its current state.
|
* Add more documentation. * Make premature binding accesses have better runtime errors. * Make accesses to `instance` not required `!`. * Rationalize our "ensureInitialized" etc logic.
* Add more documentation. * Make premature binding accesses have better runtime errors. * Make accesses to `instance` not required `!`. * Rationalize our "ensureInitialized" etc logic. Fixes flutter#64830. Most of these changes were done using `dart fix --apply`, but they have been squashed into one commit for easier merging. To see previous reviews of this PR, see flutter#83843, flutter#86388, flutter#86438, and flutter#89451.
instancenot required!.Fixes #64830.
History: This was first landed in #83843 (which was reverted in #86386), then landed in #86388 (which was reverted in #86388). Relative to the last time this landed, this adds some defensive code in
timeDilation's setter to make it not depend on the scheduler binding being initialized.Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.