Remove unused lamda captures from WebKit2
Created attachment 313313 [details] Patch
Created attachment 313316 [details] Patch
Comment on attachment 313316 [details] Patch Clearing flags on attachment: 313316 Committed r218503: <http://trac.webkit.org/changeset/218503>
All reviewed patches have been landed. Closing bug.
(In reply to WebKit Commit Bot from comment #3) > Comment on attachment 313316 [details] > Patch > > Clearing flags on attachment: 313316 > > Committed r218503: <http://trac.webkit.org/changeset/218503> This change broke the 32-bit build on macOS Sierra: https://build.webkit.org/builders/Apple%20Sierra%20Release%20%2832-bit%20Build%29/builds/2730
(In reply to Ryan Haddad from comment #5) > (In reply to WebKit Commit Bot from comment #3) > > Comment on attachment 313316 [details] > > Patch > > > > Clearing flags on attachment: 313316 > > > > Committed r218503: <http://trac.webkit.org/changeset/218503> > > This change broke the 32-bit build on macOS Sierra: > > https://build.webkit.org/builders/Apple%20Sierra%20Release%20%2832- > bit%20Build%29/builds/2730 Actually, it broke all of the Sierra builds: https://build.webkit.org/builders/Apple%20Sierra%20Release%20%28Build%29/builds/2875 https://build.webkit.org/builders/Apple%20Sierra%20Debug%20%28Build%29/builds/2867
Reverted r218503 for reason: This change broke the macOS Sierra build. Committed r218506: <http://trac.webkit.org/changeset/218506>
Planning to fix and reland this?
Let's try
Committed r218785: <http://trac.webkit.org/changeset/218785>
Re-opened since this is blocked by bug 173808
After upgrade to XCode 9.3 (30 March 2018), iOS builds are now failing with the warning: "lambda capture 'this' is not used [-Wunused-lambda-capture]" So I suspect we will eventually need to take Konstantin's patch.
Created attachment 336973 [details] Patch Just rebasing attachment 313316 [details]...
Created attachment 336975 [details] Patch
Committed r230153: <https://trac.webkit.org/changeset/230153>
<rdar://problem/39102921>
I don't actually like amount of code line overhead and fact that unused variables are captured (though maybe compiler optimizes them away, I didn't check), but in these particular usages it's fine with me. If this situation repeats in other places, we may need to consider some other solution