-
Notifications
You must be signed in to change notification settings - Fork 337
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
Prototype JSON::Coder #718
Draft
etiennebarrie
wants to merge
1
commit into
ruby:master
Choose a base branch
from
etiennebarrie:json-coder
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
+63
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I love this. That's exactly what I'd need to make sure my Doing this just doesn't feel right: class Time
def to_json(*a)
iso8601(3).to_json(*a)
end
end So far I've been relying on Oj's |
4 tasks
byroot
added a commit
to byroot/json
that referenced
this pull request
Jan 13, 2025
Ref: ruby#718 The existing `Parser` interface is pretty bad, as it forces to instantiate a new instance for each document. Instead it's preferable to only take the config and do all the initialization needed, and then keep the parsing state on the stack on in ephemeral memory. This refactor makes the `JSON::Coder` pull request much easier to implement in a performant way. Co-Authored-By: Étienne Barrié <[email protected]>
byroot
added a commit
to byroot/json
that referenced
this pull request
Jan 13, 2025
Ref: ruby#718 The existing `Parser` interface is pretty bad, as it forces to instantiate a new instance for each document. Instead it's preferable to only take the config and do all the initialization needed, and then keep the parsing state on the stack on in ephemeral memory. This refactor makes the `JSON::Coder` pull request much easier to implement in a performant way. Co-Authored-By: Étienne Barrié <[email protected]>
Co-authored-by: Jean Boussier <[email protected]>
etiennebarrie
force-pushed
the
json-coder
branch
from
January 13, 2025 14:24
889ee46
to
8bf4910
Compare
hsbt
pushed a commit
to hsbt/ruby
that referenced
this pull request
Jan 14, 2025
…sing state Ref: ruby/json#718 The existing `Parser` interface is pretty bad, as it forces to instantiate a new instance for each document. Instead it's preferable to only take the config and do all the initialization needed, and then keep the parsing state on the stack on in ephemeral memory. This refactor makes the `JSON::Coder` pull request much easier to implement in a performant way. ruby/json@c8d5236a92 Co-Authored-By: Étienne Barrié <[email protected]>
hsbt
pushed a commit
to hsbt/ruby
that referenced
this pull request
Jan 14, 2025
…sing state Ref: ruby/json#718 The existing `Parser` interface is pretty bad, as it forces to instantiate a new instance for each document. Instead it's preferable to only take the config and do all the initialization needed, and then keep the parsing state on the stack on in ephemeral memory. This refactor makes the `JSON::Coder` pull request much easier to implement in a performant way. ruby/json@c8d5236a92 Co-Authored-By: Étienne Barrié <[email protected]>
byroot
added a commit
to ruby/ruby
that referenced
this pull request
Jan 14, 2025
…sing state Ref: ruby/json#718 The existing `Parser` interface is pretty bad, as it forces to instantiate a new instance for each document. Instead it's preferable to only take the config and do all the initialization needed, and then keep the parsing state on the stack on in ephemeral memory. This refactor makes the `JSON::Coder` pull request much easier to implement in a performant way. ruby/json@c8d5236a92 Co-Authored-By: Étienne Barrié <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is still a WIP.
This API allows to use strict mode while defining how to serialize custom objects in a non-global way (without defining
to_json
on the objects' classes).It translates into another primitive object supported by JSON and leaves the serialization to the
JSON
gem.