I was somehow convinced I made that thing disabled by default …
So, yes, >> is mostly here because it was in the camlp4 extension. I’m of the opinion it should never have existed and I should not have ported it to ppx. It causes many issues, like users trying to write let f x = foo >> x or things like that. The fact that it looks like a normal operator doesn’t help.
We could deprecate it and add --sequence, then change the default state, I guess.