-
Notifications
You must be signed in to change notification settings - Fork 324
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
Make consistent types reported by the runtime with the types in the Suggestions Database #6800
Comments
Dmitry Bushev reports a new STANDUP for yesterday (2023-05-24): Progress: Started working on the issue. Reproduced the issue with the dynamic dropdown. Investigated the method pointers returned by the calls to Text.trim and Text.from_bytes. Tried to remove the .type suffix from the engine method pointer response. It should be finished by 2023-05-26. Next Day: Next day I will be working on the #6800 task. Continue working on the task |
Given https://github.com/orgs/enso-org/discussions/6762#discussioncomment-5992601 is this task still valid? |
.type
suffix to static types in the Suggestions Database
I updated the description. |
TODO section still mentions adding |
After the discussion with @Frizi, we decided that besides the method pointer, the IDE needs to know the list of arguments expected by the function. I updated the task description |
Dmitry Bushev reports a new STANDUP for today (2023-05-25): Progress: Continue working on the issue. Added a method call info with unapplied arguments in addition to the method pointer response. Started working on fixing the tests. It should be finished by 2023-05-26. Next Day: Next day I will be working on the #6800 task. Continue working on the task |
Dmitry Bushev reports a new STANDUP for the provided date (2023-05-26): Progress: Continue working on the issue. Added tests checking the applied arguments. Found an issue with the partially applied constructor. Started looking for a workaround. It should be finished by 2023-05-26. Next Day: Next day I will be working on the #6800 task. Continue working on the task |
Dmitry Bushev reports a new 🔴 DELAY for yesterday (2023-05-29): Summary: There is 4 days delay in implementation of the Make consistent types reported by the runtime with the types in the Suggestions Database (#6800) task. Delay Cause: Found an issue with how the atom constructors are created. Tried to fix it as a part of the current task but it was more complicated than I initially thought. Created a separate issue #6900 for it. |
Dmitry Bushev reports a new STANDUP for yesterday (2023-05-29): Progress: Continue working on the issue. Found the cause of why the engine reports the incorrect method call for atom constructors. Tried to find a workaround, but it turned out to be more involved than I initially thought. It should be finished by 2023-05-30. Next Day: Next day I will be working on the #6800 task. Continue working on the task |
Dmitry Bushev reports a new STANDUP for today (2023-05-30): Progress: Continue working on the issue. Reported an issue with the incorrect method pointer for atom constructors. Updated the language server API. Updated the GUI to support the new API. Tested the new API in IDE. Updated the PR. It should be finished by 2023-05-30. Next Day: Next day I will be working on the #6800 task. Continue working on the task |
close #6800 Update the `executionContext/expressionUpdates` notification and send the list of not applied arguments in addition to the method pointer. # Important Notes IDE is updated to support the new API.
The #6903 should fix expression updates for partially applied constructors. |
related #6715
Runtime type representation report static types with the
.type
suffix. In contrast, the suggestions database has theis_static
flag instead. This creates inconsistencies in the language server API.TODO
The text was updated successfully, but these errors were encountered: