Bug 300747

Summary: [WTF] Fix -Wc++23-lambda-attributes warnings
Product: WebKit Reporter: David Kilzer (:ddkilzer) <ddkilzer>
Component: Web Template FrameworkAssignee: David Kilzer (:ddkilzer) <ddkilzer>
Status: RESOLVED FIXED    
Severity: Normal CC: webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

David Kilzer (:ddkilzer)
Reported 2025-10-14 16:32:01 PDT
Fix -Wc++23-lambda-attributes warnings in various WTF source files. ``` WebKitBuild/Release/usr/local/include/wtf/ThreadSafeWeakPtr.h:92:44: warning: an attribute specifier sequence in this position is a C++23 extension [-Wc++23-lambda-attributes] 92 | auto deleteObject = [this, object] SUPPRESS_UNCOUNTED_LAMBDA_CAPTURE { | ^ WebKitBuild/Release/usr/local/include/wtf/ThreadSafeWeakPtr.h:244:44: warning: an attribute specifier sequence in this position is a C++23 extension [-Wc++23-lambda-attributes] 244 | auto deleteObject = [this] SUPPRESS_UNCOUNTED_LAMBDA_CAPTURE { | ^ WebKitBuild/Release/usr/local/include/wtf/RunLoop.h:208:71: warning: an attribute specifier sequence in this position is a C++23 extension [-Wc++23-lambda-attributes] 208 | : Timer(WTFMove(runLoop), description, [object, function] SUPPRESS_UNCOUNTED_LAMBDA_CAPTURE { // The Timer's owner is expected to cancel the Timer in its destructor. | ^ WebKitBuild/Release/usr/local/include/wtf/RunLoop.h:218:71: warning: an attribute specifier sequence in this position is a C++23 extension [-Wc++23-lambda-attributes] 218 | : Timer(WTFMove(runLoop), description, [object, function] SUPPRESS_UNCOUNTED_LAMBDA_CAPTURE { // The Timer's owner is expected to cancel the Timer in its destructor. | ^ ```
Attachments
Radar WebKit Bug Importer
Comment 1 2025-10-14 16:32:25 PDT
David Kilzer (:ddkilzer)
Comment 2 2025-10-14 22:13:14 PDT
EWS
Comment 3 2025-10-15 19:56:03 PDT
Committed 301598@main (1e7334780f9b): <https://commits.webkit.org/301598@main> Reviewed commits have been landed. Closing PR #52369 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.