Investigate If The Filtered Object Can Be Turned Into A Struct, To Create Less GC Pressure #12
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: owner/RSE#12
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As the title suggests, this object is quite big, and if possible, would be nice to make into a struct of sorts. Needs testing first, of cause. But we could make it so there is like an id for each different type of value.
Like "keep-alive" would equal to "15". Or "keep-alive,cache,gzip" would equal to "62".
But if that's too much work, then maybe just change where possible. Like instead of having "TlsV1.3", then just "1.3", because everyone just uses TLS anyway.
Investigate If This Object Can Be Turned Into A Struct, To Create Less GC Pressureto Investigate If The Filtered Object Can Be Turned Into A Struct, To Create Less GC PressureAfter investigating, I've come to the conclusion that it wouldn't be worth it. There's too many properties that would have to be re-worked, and too many methods that would have to be reworked as well.