Raoul Hidalgo Charman

Don't think the test failure is related to any of my changes, is that a known flaky test?

@raehik

Hmm yeah perhaps just the parent expression instead of the zipper would be simpler, just update it every time you go down the tree. I've not had to yet but...

Hmmm I see. Would there be some way of indicating to the monadic reprinter which movements have been taken? Although I'm unsure if that would fit nicely into how `getRefactorings`...

Why exactly is that parsed differently? Is there anything significant about bracketed arguments?

Oh I was unaware of that too, that's a feature that introduces some unfortunate syntactical ambiguity. Not sure what the best way to handle that is. Obviously `foo((var)*2)` should still...

This is on master, and I get that error code with or without `--typecheck` and on different Fortran versions (66, 77, 90, 95). The initial `ProgramFile` is a left over...

Huh that is odd, I definitely get it to work with standard unix line endings. This is on mac, just tried on a linux machine and it does also successfully...

Yes sorry should have said, we use legacy 77 for everything so that's what I default to when running fortran-src :) This isn't hugely problematic btw, I've only encountered one...

I have recently been thinking about this, as there are cases where multiline conditionals may be refactored and we want to avoid losing inline comments which is a bit trickier...