-
Notifications
You must be signed in to change notification settings - Fork 323
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
Reference rewriting #8683
Comments
Keziah Wesley reports a new STANDUP for yesterday (2024-01-04): Progress: Designing/implementing reference-rewriting APIs and introducing some linear typing to prevent "temporarily" invalid module states, which are not compatible with the reference rewriting API. It should be finished by 2024-01-08. Next Day: Next day I will be working on the #8683 task. Finish implementing reference rewriting and related APIs. |
Keziah Wesley reports a new STANDUP for the last Friday (2024-01-05): Progress: Finish reference rewriting. It should be finished by 2024-01-08. Next Day: Next day I will be working on the #8683 task. Finish task, resume implementing sync. |
Adam Obuchowicz reports a new 🔴 DELAY for today (2024-01-09): Summary: There is 2 days delay in implementation of the Reference rewriting (#8683) task. Delay Cause: Kaz took day off, and issues were hard to debug by me and Paweł |
Adam Obuchowicz reports a new STANDUP for today (2024-01-09): Progress: Pair-debugged the Kaz's PR about AST reference rewriting. Had some discussions, and made a working code. It should be finished by 2024-01-10. Next Day: Next day I will be working on the same task. try to fix last issues related to widget updating; then do next stuff from backlog |
Keziah Wesley reports a new STANDUP for yesterday (2024-01-09): Progress: Debugging issues with ID stability. It should be finished by 2024-01-10. Next Day: Next day I will be working on the #8237 task. Resume implementing sync. |
AST APIs need to support two distinct kinds of update to an expression:
MutableModule.set
).The new substitution operation will provide a way to handle the case of an expression being moved within the module without the need to alter its ID.
The text was updated successfully, but these errors were encountered: