00:44 <mbj> snusnu: hola

17:00 <mbj> dkubb: fuck, found something REALLY hard to unparse.

17:01 <mbj> dkubb: foo = bar while foo

17:01 <mbj> dkubb: because the condition is actually an lvar read, I cannot turn it into: while foo; foo = bar; end

17:01 <mbj> dkubb: And the lvar foo, just got introduced.

17:02 <mbj> dkubb: So I have to support emitting control keyword as postconditions with arbitrary deep checking for lvar assignments.

17:02 <mbj> dkubb: x && foo = bar while foo

17:02 <mbj> dkubb: Here I have to "know" foo gets assigned in the body of while, so controll condition is an lvar read.

17:03 <mbj> dkubb: So I'll have to support "post controll with lvar assignment detection" for ALL control statments.

17:03 <mbj> dkubb: That code is very rare.

17:05 <mbj> dkubb: This is the problematic code: https://github.com/chriseppstein/compass/blob/stable/lib/compass/sass_extensions/functions/image_size.rb#L92

17:05 <mbj> dkubb: There is NO other way to reproduce this line via while as postcondition.

17:05 <mbj> Now I hate lvar / private send ambiguity in ruby :D

17:06 <mbj> Or postcontroll statments.

17:27 <mbj> dkubb: Solution found.

17:28 <mbj> dkubb: Gonna inspect the nodes conditions and branches, searching for lvar assignments in body that must preceed the condition when parsed.

17:28 <mbj> dkubb: preorder = (lvar_assignments(body) & lvar_reads(condition)).any?