Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@robert-ancell
Copy link
Contributor

The existing code worked, but it cleared the objects before calling init_keyboard. This made it look like init_keyboard might leak the existing values. If a third case was added later where init_keyboard was called it would leak if the caller didn't clear the objects before calling it.

The existing code worked, but it cleared the objects before calling init_keyboard.
This made it look like init_keyboard might leak the existing values. If a third
case was added later where init_keyboard was called it would leak if the caller
didn't clear the objects before calling it.
@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact "@test-exemption-reviewer" in the #hackers channel in Chat (don't just cc them here, they won't see it! Use Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@Hixie
Copy link
Contributor

Hixie commented Feb 8, 2024

test-exempt: code refactor with no semantic change

@robert-ancell robert-ancell merged commit 084bd0b into flutter:main Feb 8, 2024
@robert-ancell robert-ancell deleted the clear-before-set branch February 8, 2024 03:21
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Feb 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants