Remove WTF::Optional synonym for std::optional, using that class template directly instead
Created attachment 430130 [details] Patch
Thanks for the patch. If this patch contains new public API please make sure it follows the guidelines for new WebKit2 GTK+ API. See https://trac.webkit.org/wiki/WebKitGTK/AddingNewWebKit2API This patch modifies the inspector protocol generator. Please ensure that you have rebaselined any generator test results (i.e., by running `Tools/Scripts/run-inspector-generator-tests --reset-results`)
Created attachment 430131 [details] Patch
Comment on attachment 430131 [details] Patch R=me once the bots are happy.
Created attachment 430132 [details] Patch
Committed r278253 (238290@main): <https://commits.webkit.org/238290@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 430132 [details].
<rdar://problem/78664888>
Seems to have broken the Windows build: https://build.webkit.org/#/builders/67/builds/3216/steps/8/logs/errors The issue is not super obvious to me.
(In reply to Chris Dumez from comment #8) > Seems to have broken the Windows build: > https://build.webkit.org/#/builders/67/builds/3216/steps/8/logs/errors > > The issue is not super obvious to me. The include is there so I am wondering if there is a `#define optional` somewhere that is polluting us?
(In reply to Chris Dumez from comment #9) > (In reply to Chris Dumez from comment #8) > > Seems to have broken the Windows build: > > https://build.webkit.org/#/builders/67/builds/3216/steps/8/logs/errors > > > > The issue is not super obvious to me. > > The include is there so I am wondering if there is a `#define optional` > somewhere that is polluting us? Or maybe that bot just needs a clean build. Some of the build output still refers to "Optional": 'Inspector::Protocol::Helpers::Optional': definition of dllimport data not allowed
Maybe Windows uses a different "erb" file? The EWS Windows build didn’t fail, though!
(In reply to Darin Adler from comment #11) > Maybe Windows uses a different "erb" file? The EWS Windows build didn’t > fail, though! And the boy recovered on its own on the next build. It was an incremental build issue I believe.
Follow-up build fix in <https://commits.webkit.org/r278319>.
(In reply to Chris Dumez from comment #13) > Follow-up build fix in <https://commits.webkit.org/r278319>. And <https://commits.webkit.org/r278320>
Very nice!
Will the style checker tell me if I use the old thing? A webkit-dev email is probably justified too.
We can add it to the style checker, but also it won’t compile.
Not compiling seems sufficient. But a webkit-dev heads-up would be welcome.
(In reply to Simon Fraser (smfr) from comment #18) > Not compiling seems sufficient. But a webkit-dev heads-up would be welcome. https://lists.webkit.org/pipermail/webkit-dev/2021-June/031875.html