I agree that this is not worth the effort.
A good way to look at it is “I am sure this code is html_safe, so I can unescape it.”
Otherwise “non_escapify_html” sounds pretty rails-y.
Interesting. I know people generally advise to use:
raw()
``
instead of
.html_safe
``
For naming, what about:
.do_not_escape
``
JP