sdk
sdk copied to clipboard
Support for hot reload in DDC
This is a meta issue to track any individual work towards support for hot reload in DDC.
The table below is just an approximation. It is meant to be updated periodically as we figure out plans, steps, and complete tasks.
- Testing preparations:
- [ ] test harness for coverage and faster team iteration
- Representation changes
- [ ] Disentangle libraries from modules
- [ ] Changes to library representation to allow updates to top-levels and classes
- [x] Enable new runtime type representation by default
- [ ] Ensure indirection: all member access, including fields, can be updated
- [ ] Changes to class representation to stop capturing type parameters via closures
- Hot reload mechanics
- [ ] Updating library and class objects in-place
- [ ] Replacing field initializers to ensure existing objects reflect the correct value of newly added fields
- [ ] Detection of rejection cases
- Debugging support
- [ ] Version management and source-map support
- Integration
- [ ] Unify module systems
- [ ] Add hot reload workflows into dwds and flutter-tools