Will the Operations from the Affine dialect also be renamed? I feel like affine::AffineForOp could be renamed to affine::ForOp now.

Thank you, @ftynse
Could you push the patch when you get a chance since I don't have permissions?

Also fix the tests

merge my commits into one

Add braces for readability

In D147345#4242641, @springerm wrote:

This change makes sense to me. It's been a while since I looked at this particular part of the file though. Could you go back in the Github history and also add the original author of this function? (The file was moved around a few times.)

@springerm Since you have been working on a restructuring of the FlatAffineValueConstraints / Affine Analysis classes and are working on the ValueBoundsOpInterface, which all seem related, could you comment on this?

Could someone with repository access push this patch? Thanks in advance :)

In D147384#4238659, @mehdi_amini wrote:

Is the cast still needed now? I would think that getOperation() returns directly the interface now

Remove the cast because getOperation() already returns the Interface.

To clarify a little more, because I saw that there have been a few changes to these files recently and I'm not entirely sure whether the current behavior of the function might be intentional: