public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "milasudril at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113754] New: GCC complains when using a type that depends on lambda Date: Sun, 04 Feb 2024 09:38:08 +0000 [thread overview] Message-ID: <bug-113754-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113754 Bug ID: 113754 Summary: GCC complains when using a type that depends on lambda Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: milasudril at gmail dot com Target Milestone: --- I tried to use template<typename T, auto DeleteFn> using unique_ptr_deleter = std::unique_ptr<T, decltype([](T* obj) { DeleteFn(obj); })>; As described by https://andreasfertig.blog/2022/08/cpp-insights-lambdas-in-unevaluated-contexts/ It works well as long as I do not try define it in a header file. If gcc detects a from a header file that uses unique_ptr_deleter, I get the warning lib/array_classes/./memory_block.hpp:12:8: error: 'memory_block' has a field 'unique_ptr_deleter<void, free> terraformer::memory_block::m_pointer' whose type has internal linkage [-Werror=subobject-linkage] Clang do generate any warnings. Stand-alone snippet to reproduce the issue: #include <memory> #include <cstdlib> # 7 "lib/array_classes/./memory_block.hpp" template<class T, auto DeleteFn> using unique_ptr_deleter = std::unique_ptr<T, decltype([](T* obj) { DeleteFn(obj); })>; class memory_block { public: private: unique_ptr_deleter<void, free> m_pointer; }; # 4 "lib/array_classes/memory_block.test.cpp"
next reply other threads:[~2024-02-04 9:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-04 9:38 milasudril at gmail dot com [this message] 2024-02-04 12:42 ` [Bug c++/113754] " pinskia at gcc dot gnu.org 2024-04-13 8:34 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113754-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).