Mention the @trace macro in readme

[Evizero]

We should advertise this functionality

[tbreloff]

Yes, though I'm not sure its ready for prime time yet. I want to use it a bit and maybe make some changes. I was thinking about a second "trace_iter" macro which does what trace currently does. It would also be nice to also support "dynamic tables" with strongly typed fields under the same framework for those cases where you always add the same fields in a loop and want performance. We should examine the DataStreams world and see if we can overlap.

On Wednesday, August 24, 2016, Christof Stocker [email protected] wrote:

We should advertise this functionality

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JuliaML/ValueHistories.jl/issues/9, or mute the thread https://github.com/notifications/unsubscribe-auth/AA492kQqLKXM1rmO0lZ8XzTalvCgIR3aks5qi9ujgaJpZM4JrqHL .

[Evizero]

all good ideas

[cossio]

It would be nice that the @trace macro had a variant where you didn't have to specify the iteration number, so it would just push! and increment by one whatever the previous iteration number was.