-
Notifications
You must be signed in to change notification settings - Fork 12
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
derive: add benchmark #14
Conversation
rinja_derive_standalone/Cargo.toml
Outdated
[features] | ||
default = ["__standalone"] | ||
__standalone = [] | ||
config = ["serde", "basic-toml"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing the :dep
part you mentioned. ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hehe, yeah. I leave this task to tomorrow-me. :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve this way of seeing things! 😆
Looks like a great start! Can you add documentation on how to run these benchmarks as well please? |
1719626
to
e8e59fc
Compare
Yup, added. |
Awesome, when the |
Just need to fix the merge conflict and it can get merged. :) |
This PR adds the crate "rinja_derive_standalone", which is just like "rinja_derive", though not a "proc_macro". This way we can easily expose it's internals for testing and benchmarking. Right now, the PR is more or less a prove of concept, and it probably needs a handful more useful benchmark use cases to be worth the hassle.
e8e59fc
to
1ce549d
Compare
Thanks! |
This PR adds the crate "rinja_derive_standalone", which is just like "rinja_derive", though not a "proc_macro". This way we can easily expose it's internals for testing and benchmarking.
Right now, the PR is more or less a prove of concept, and it probably needs a handful more useful benchmark use cases to be worth the hassle.
Resolves #12.