You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've moved away from the (field f) form of referencing fields and instead have used automatically generated accessor methods: (send this f).
We should do the same for (set-field! f x). I propose we generate mutator methods (send this f! x).
There is some potential for this going wrong, eg if you have a class with fields f and f!, then method f! is ambiguous, but so long as this is a syntax error, it seems fine.
The text was updated successfully, but these errors were encountered:
We've moved away from the
(field f)
form of referencing fields and instead have used automatically generated accessor methods:(send this f)
.We should do the same for
(set-field! f x)
. I propose we generate mutator methods(send this f! x)
.There is some potential for this going wrong, eg if you have a class with fields
f
andf!
, then methodf!
is ambiguous, but so long as this is a syntax error, it seems fine.The text was updated successfully, but these errors were encountered: