location missing from unsupported class body statement error #112

Closed
opened 2021-11-23 17:52:33 +08:00 by sb10q · 3 comments
Owner
pyo3_runtime.PanicException: called `Result::unwrap()` on an `Err` value: "unsupported statement type in class definition body"
``` pyo3_runtime.PanicException: called `Result::unwrap()` on an `Err` value: "unsupported statement type in class definition body" ```
Author
Owner

@ychenfo is there still more work you need to do in that err_msg_improvement branch or should we merge?

@ychenfo is there still more work you need to do in that err_msg_improvement branch or should we merge?
Collaborator

@ychenfo is there still more work you need to do in that err_msg_improvement branch or should we merge?

Oh I think merging this should solve these practical issues mentioned. Previously I tabled this because I plan to add file name in this branch, now we add file name to the AST so I think this branch can be merged first?

After adding file names some of the error messages improvements in this patch will need to be revisited though, I can send another patch for it after adding file name in AST.

> @ychenfo is there still more work you need to do in that err_msg_improvement branch or should we merge? Oh I think merging this should solve these practical issues mentioned. Previously I tabled this because I plan to add file name in this branch, now we add file name to the AST so I think this branch can be merged first? After adding file names some of the error messages improvements in this patch will need to be revisited though, I can send another patch for it after adding file name in AST.
sb10q referenced this issue from a commit 2021-12-22 08:52:20 +08:00
Author
Owner

Previously I tabled this because I plan to add file name in this branch, now we add file name to the AST so I think this branch can be merged first?

It is generally better to avoid bundling too many things into one PR anyway.

> Previously I tabled this because I plan to add file name in this branch, now we add file name to the AST so I think this branch can be merged first? It is generally better to avoid bundling too many things into one PR anyway.
sb10q closed this issue 2021-12-22 08:53:18 +08:00
ychenfo referenced this issue from a commit 2021-12-27 16:57:43 +08:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/nac3#112
No description provided.