m.x++ not working #189
Comments
|
also |
ldemailly
added a commit
that referenced
this issue
Sep 4, 2024
…for forcing local scope variable creation; cache bug fix (#206) * Reference type * progress: force create and make refs unless := (future) or fn params (in this commit) * Adding := as local (re)definition/copy. seemingly working version overall * Adding a few basic tests * fix the loop/review comment - add failing test * fix makefile generate, fix ref of ref case * cover post and pre incr/decr. add example of state in lambda * Fix reference loops, add tests * add direct state from params example * prevent aliases upstack/avoid indirect loops; fix caching bug and add test for it using 2 level deep rand() * Catch errors like m[xy++] if xy is not incrementable and lay ground work for #189 (failing test) * Clean up index expression with . so it actually errors out for m.xy++ pending implementation * Reduce greatly the peppering of object.Value() and return the actual type for REFERENCE instead of referenced object's type * move evalinternal -> eval but need some negative additional testing that return unwrap isn't now too early * Adding test of return bubbling up correctly inside for loops and nesting * copy multi platform fortio workflow (and somehow setup-go action is old here) * maybe fix testscript on windows * Give up on testscript and windows for now * fix bug index assignment missing deref
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
it parses as
== Parse ==> (m.(x++))
which is why it doesn't work as it would increment an unrelated variable but actually just uses "x++" as the string key
The text was updated successfully, but these errors were encountered: