I disagree that this isn't a bug. Or, perhaps it's better to say it is surprising to see this error raised. If it isn't a bug, it might be helpful to know why it behaves this way for vector-offset and another way for slope.
Using the vector-offset constraint on the ETW and setting the parents to CL and EP raises the recursive constraint error.
Using the slope constraint on the ETW and setting the parent to CL and locking the slope to follow the slope between CL and EP does not raise the recursive constraint error.
I'd always considered vector-offset (when the offset given is 0) to be shorthand for using the slope constraint, so to me they should yield identical performance and identical errors. If you can explain to me how my understanding is fundamentally flawed, I'm all ears.
Using the vector-offset constraint on the ETW and setting the parents to CL and EP raises the recursive constraint error.
Using the slope constraint on the ETW and setting the parent to CL and locking the slope to follow the slope between CL and EP does not raise the recursive constraint error.
I'd always considered vector-offset (when the offset given is 0) to be shorthand for using the slope constraint, so to me they should yield identical performance and identical errors. If you can explain to me how my understanding is fundamentally flawed, I'm all ears.