-
Notifications
You must be signed in to change notification settings - Fork 30k
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
dgram: prevent disabled optimization of bind() #4613
Conversation
Have you thought about refactoring it to not use |
I went for minimal impact on this one. shrug |
Well, LGTM either way. |
LGTM, but would it be cleaner to just do |
@cjihrig |
I don't think it should make a difference in that case. |
LGTM if CI is green |
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized.
a2b4c49
to
2ffd365
Compare
Updated PR to simplify things as suggested. CI again for fun: https://ci.nodejs.org/job/node-test-pull-request/1216/ |
Ah, much better. LGTM. |
LGTM |
1 similar comment
LGTM |
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized. PR-URL: #4613 Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Landed in 88b2889 |
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized. PR-URL: #4613 Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized. PR-URL: #4613 Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized. PR-URL: #4613 Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized. PR-URL: nodejs#4613 Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized. PR-URL: nodejs#4613 Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized. PR-URL: nodejs#4613 Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Reassigning a named parameter while also using the arguments object causes the entire function to never be optimized.