-
Notifications
You must be signed in to change notification settings - Fork 32
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
create performance evaluation test for _to_string() family of functions #129
Comments
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 29, 2016
rgerhards
added a commit
to rgerhards/libfastjson
that referenced
this issue
Nov 30, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to have some tooling to evaluate performance of different implementations. Ideally, this should be automatically, but at least semi-automatically (with some need for manual action but a clearly documented way of doing this).
Among others, this is useful for evaluating #120, but also for all further refactoring work.
The text was updated successfully, but these errors were encountered: