Sadly, there is no way to fix this without patching Haml or renaming Haml::Rails.

Happily, nex3 has invited me to submit Haml::Rails as a patch to Haml itself, which should resolve that particular problem.

how nice!

Is it worth me fixing this in Haml, or is the integration going to happen quickly enough that it won't matter?

Well, referring to the top-level Rails constant by ::Rails is always a good idea... Haml breaking if someone ever defines a Haml::Rails class seems not that great. I was planning on just adding that as part of my patch (which unfortunately looks like it's going to take until next week, sorry. Work deadlines snuck up on me.)

Ops. Rails again breaks things :) What would be a temporary workaround?

s/Rails/::Rails/g in haml/util.rb of haml gem.

nex3/haml@1746cb1

Thanks a lot.
Cheers.