This repository was archived by the owner on Feb 25, 2025. It is now read-only.
Remove unused setPersistentIsolateData function #30795
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FlutterDartProject.setPersistentIsolateDatais neither a public API nor is it used anywhere internally. And its purpose is easily misunderstood by contributors.It seems that there was a plan to use persistent isolate data to store some persistent data such as user settings data and lifecycle state, but we never started doing it.
Even if we need to use it to store user settings data and lifecycle state in the future, we still should not set it by
FlutterDartProject.setPersistentIsolateData, because lightweight engines share the sameFlutterDartProject, while each engine needs to have its own settings data and lifecycle state. SoRunConfigurationwould be a better choice thanFlutterDartProject.setPersistentIsolateData.Pre-launch Checklist
writing and running engine tests.
///).