-
Notifications
You must be signed in to change notification settings - Fork 63
Unsafe #91
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
Unsafe #91
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lavalamp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This brings the total improvement to:
|
The unsafe bit is key, sadly-- removing it I get
|
I've modified this to do a less unsafe thing with the unsafe package. (performance is the same.) |
I think this is OK. I don't have much knowledge about jsoniter though. |
/lgtm Should we rebase before merging? |
/lgtm |
rebased, but I see you already noticed... :) |
Only the last commit is new. These numbers are for just that commit.
Unfortunately I don't think I can give deserialize the same treatment without making jsoniter changes :/
Note that this makes use of the unsafe package, I need changes to jsoniter to avoid that.
Jsoniter's pools are apparently... not for the purpose of doing optimal memory management.