The tag-choosing is done entirely at compile-time, so as long as Haml is being cached it shouldn't affect performance at all. Even if it's not, it's not using any extra context - just the same data that's used to remember which tags to close.
Nate Vack wrote: > Awesome idea... my only question: what's the performance hit like? > Does bringing the extra context along hurt much? > > -Nate > > On Mar 4, 7:24 pm, Nex3 <[EMAIL PROTECTED]> wrote: > >> Hey folks, >> >> When Haml was originally created, Hampton decided to make it even >> easier to create divs than it was to create other sorts of tags by >> making divs the default. >> >> Mislav Marohnić had an interesting idea for extending this. In some >> cases, divs are invalid - within a p tag, for example, or an ol. What >> if instead of producing a div, an implicit tag would create whatever >> makes sense? A span, an li, maybe a tr or td. >> >> There are a few potential issues with this. It makes Haml's output >> more dependent on the document context than it usually is, and might >> break a few templates. On the other hand, you should be thinking about >> the context in which you use divs anyway, and any templates it breaks >> are invalid anyway. >> >> So I wanted to get the community's opinion on this. Is this something >> you'd like? Something you'd dislike? Or does it not really matter to >> you? >> >> If you want to try it out, grab Mislav's Haml fork at >> git://github.com/mislav/haml.git. >> >> - Nathan >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
