Job Vranish
I am well aware of the usual ST/IORefs as the usual solutions to data mutability in haskell. I very very much understand purity, and why it is a good thing, and why we should try to stay away from IO and ST as much as possible. I am very much away that even if I had such a function that it will probably break everything. I am not just trying to make things run faster.
What I am trying to do is hyper unusual and I really do need an unsafeHorribleThings to do it.
Well, is purpose of this a big secret? Maybe if you describe the whole direction of such efforts, somebody could propose better solution that satisfies your needs. I recommend you to describe semantics of unsafeHorribleThings in details, and in what exact cases this could be useful.