09:35 <ddfreyne> guardian: I understand, but there is no guarantee in which order nanoc compiles items (and thus calls tabs())

09:36 <ddfreyne> guardian: So there's the chance of getting different outputs every time you compile

09:36 <ddfreyne> guardian: Even worse, this requires *all* items to be recompiled all the time in order to work properly

09:51 <guardian> ddfreyne: I don't need items to be compiled in same order every time

09:52 <guardian> ddfreyne: what's the exception raised when an item asks for another item's compiled_content but other item isn't compiled yet?

16:34 <ddfreyne> guardian: http://nanoc.ws/docs/api/Nanoc/Errors/UnmetDependency.html

18:24 <bobthecow> ddfreyne: iirc it's per-item order that matters, not order between items. i.e. when compiling /foo/, multiple calls to tabs() will result in tabs1 tabs2, etc.

18:24 <bobthecow> but when compiling /bar/, it will also result in tabs1, tabs2