Use or not of ROP terminology

[mavnn]

Because I think this is a better forum than twitter!

@tpetricek do you mind explaining your opposition to using ROP based names? I'm not sure I'm seeing the issue yet, especially if we have a two sentence byline of "this is an either monad under the hood" somewhere.

It feels like it throws away a lot of Scott's good work on explaining things in nice easy to understand language.

[pblasucci]

I like the ROP metaphor, but agree the naming is a bit "off" in code. I just shot off a PR that changes the computation expression from rop {} to attempt{}. However, I feel STRONGLY that the docs should continue to describe things using the railway metaphor.

[TWith2Sugars]

When I messed around with my own implementation of a ROP builder I ended up naming itattempt too. Felt like a good fit to me.

[Kurren-N]

attemptseems more natural, in my view