Closed jecisc closed 4 years ago
damn once again it should either treat it as error node (worst case) but ideally be able to infer that this is a message send. i'll make an intermediate fix but this should be left open until we figure it out, along with the other issue (array, i think)
PR : https://github.com/pharo-project/pharo/pull/4215 again, just an intermediate fix to stop it from breaking
as we fixed the bug reported, we can close this.
@MarcusDenker we did fix the DNU on assignment node, yes, but i was keeping this open because this shouldn't have been an assignment node in the first place... and i think we are yet to figure that one out. Although i can create a separate issue and reference this one, if that's better.
My philosophy is to always open new issue: if someone reports a bug and I fix it, it is fixed. If there is something else, it is something else. Because it is very annoying to read through all the things that area not a problem anymore.. nobody understands anything if an issue starts with multiple comments related to something that is already done.
Ok i created a separate issue, closing this one.
I got this error with this code:
My cursor was at
self class envi
and I as typing there.