Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mention the @trace macro in readme #9

Open
Evizero opened this issue Aug 24, 2016 · 3 comments
Open

Mention the @trace macro in readme #9

Evizero opened this issue Aug 24, 2016 · 3 comments

Comments

@Evizero
Copy link
Member

Evizero commented Aug 24, 2016

We should advertise this functionality

@tbreloff
Copy link
Member

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 notifications@github.com
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
#9, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AA492kQqLKXM1rmO0lZ8XzTalvCgIR3aks5qi9ujgaJpZM4JrqHL
.

@Evizero
Copy link
Member Author

Evizero commented Aug 24, 2016

all good ideas

@cossio
Copy link
Contributor

cossio commented May 11, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants