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.

Sign up for GitHub

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

Jump to bottom

Evaluate whether boostjson or other solutions introduce problems supporting its use in contracts #317

Closed
stephenpdeos opened this issue Oct 13, 2022 · 2 comments
Closed

Evaluate whether boostjson or other solutions introduce problems supporting its use in contracts #317

stephenpdeos opened this issue Oct 13, 2022 · 2 comments
Assignees
@bhazzard
Labels
triage

Comments

@stephenpdeos
Copy link
Member

Report back size differences and CPU usage between rapidjson and boostjson for a few examples
@heifner
Copy link
Member

heifner commented May 3, 2023

This may be a moot issue depending on: eosnetworkfoundation/product#160

@bhazzard bhazzard self-assigned this Jun 8, 2023
@bhazzard bhazzard added triage and removed 👍 lgtm labels Jun 29, 2023
@bhazzard
Copy link

bhazzard commented Oct 5, 2023

Closing because decision is made already (boostjson)

@bhazzard bhazzard closed this as completed Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bhazzard bhazzard

Labels
triage
Projects
Team Backlog
Archived in project
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bhazzard @heifner @stephenpdeos @enf-ci-bot