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.

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

⚡ Use frozen const when parsing empty arrays #283

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nevans
Copy link
Collaborator

@nevans nevans commented May 19, 2024

TODO:

NOTE: this will be considered a breaking change, because some libraries may rely on responses being mutable. (See e.g: #262) The kind thing to do would be to add a config var and a conditional, however that may impact performance... and performance is the primary reason for this PR. Maybe the mail gem will accept a PR to not mutate search responses? (done)

@nevans nevans added the v0.5 label May 19, 2024
@nevans nevans added this to the v0.5 milestone May 19, 2024
@nevans nevans removed the v0.5 label May 19, 2024
@nevans nevans force-pushed the parser/frozen-private-EMPTY_ARRAY-const branch 3 times, most recently from fc08916 to 9771e1a Compare June 22, 2024 16:16
@nevans nevans force-pushed the parser/frozen-private-EMPTY_ARRAY-const branch from 9771e1a to 3b0bed8 Compare June 26, 2024 14:56
@nevans nevans modified the milestones: v0.5, v0.6 Jun 29, 2024
@nevans nevans force-pushed the parser/frozen-private-EMPTY_ARRAY-const branch from 3b0bed8 to 801b4ae Compare October 12, 2024 14:42
@nevans nevans force-pushed the parser/frozen-private-EMPTY_ARRAY-const branch from 801b4ae to 090d11a Compare October 29, 2024 18:08
@nevans nevans force-pushed the parser/frozen-private-EMPTY_ARRAY-const branch from 090d11a to 697fde6 Compare November 8, 2024 22:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant