<bobthecow>
basically, you could do this lots of ways, but the dumbest way (actually pre-filling all the attributes you'll need on items) turns out to be the best way for nanoc.
<bobthecow>
because it tracks dependencies.
<bobthecow>
some people do crazy things with caching, or memoizing, or any number of things...
<tom[]>
this is what i was trying to do but i got the Frozen error
VitamineD has quit [Quit: Leaving.]
<bobthecow>
but just preprocessing everything and storing in the actual attributes is the way to go.
<bobthecow>
yeah, you get frozen errors every time you do anything *after* preprocessing.
<bobthecow>
if you try to change items while compiling, nanoc has no way of tracking dependencies.
<bobthecow>
but during preprocessing is a free-for-all.
<bobthecow>
change them however you want :)
<tom[]>
the error message was remarkably comprehensive, explaining about the need for compiler optimization
VitamineD has joined #nanoc
<tom[]>
thanks again, bobthecow. preprocess is the balls!
<bobthecow>
no problem :)
<tom[]>
any idea what using guard gives "LoadError: cannot load such file -- nanoc/toolbox" while running the nanoc command works normally?
<tom[]>
s/what/why/
<bobthecow>
nope, but ddfreyne might.
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
VitamineD has quit [Read error: Connection reset by peer]