support augmented assignments #82

New Issue

sb10q · 2021-11-10T13:53:12+08:00

sb10q commented

2021-11-10 13:53:12 +08:00

for example

count += 1

pyo3_runtime.PanicException: called `Result::unwrap()` on an `Err` value: "Unsupported statement type at line 360 column 13"

for example ``` count += 1 ``` ``` pyo3_runtime.PanicException: called `Result::unwrap()` on an `Err` value: "Unsupported statement type at line 360 column 13" ```

sb10q commented

2021-11-10 19:00:15 +08:00

Poster

This is actually fairly common in ARTIQ drivers, and while it can be worked around it should be quick to implement instead.

sb10q added the

high-priority

label 2021-11-10 19:00:20 +08:00

ychenfo was assigned by sb10q

2021-11-11 23:09:54 +08:00

sb10q referenced this issue from a commit

2021-11-13 12:25:46 +08:00

nac3core: AugAssign support (#82)

sb10q commented

2021-11-13 12:30:15 +08:00

Poster

What to do about the unimplemented!() call for unsupported types? Eventually we cannot leave it like that for the users.
If we support AugAssign only for those scalar types this is fine IMO, but there should be a good error message when the user tries to do something else.

What to do about the ``unimplemented!()`` call for unsupported types? Eventually we cannot leave it like that for the users. If we support ``AugAssign`` only for those scalar types this is fine IMO, but there should be a good error message when the user tries to do something else.

sb10q removed the

high-priority

label 2021-11-13 12:31:05 +08:00

sb10q added this to the Alpha milestone 2022-04-12 09:43:05 +08:00

ychenfo referenced a pull request that will close this issue

2022-04-18 05:04:07 +08:00

Custom Defined Operators Behavior Support #268

sb10q closed this issue

2022-04-18 15:31:57 +08:00

Sign in to join this conversation.