Rewrite Subscription as a closure factory for byte shaving #1755
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 PR:
Subscription
class to be a closure factory instead, which should shrink minified size by about 300 bytesbindActionCreators
back to the simpler version we had when we copied it over to save a few more bytesThe
Subscription
class is one of the two biggest pieces when you importuseSelector
, the other being theuseSelector
hook itself. I noticed that when we convertedSubscription
to TS, we added some uses of the?.
optional chaining operator, but each of those gets compiled into several null/undefined checks.I went to change the optional chaining back to simple
if
clauses instead, but then realized that if I switched this to be a closure factory, I could drop all the uses ofthis
as a bonus.We can apply the same changes over in the 7.2 line as well.