public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "konstantinua00 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/101870] New: std::lerp is missing Arithmetic overloads Date: Thu, 12 Aug 2021 02:32:31 +0000 [thread overview] Message-ID: <bug-101870-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101870 Bug ID: 101870 Summary: std::lerp is missing Arithmetic overloads Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: konstantinua00 at gmail dot com Target Milestone: --- According to C++20 standard paragraph 20.8.1.2, std::lerp is not an exception to expansion of acceptable parameters to integral and mixed floating point types. I.e. overload 4) from https://en.cppreference.com/w/cpp/numeric/lerp is missing. Example code (compile with -std=c++20): #include<cmath> int main() { std::lerp(int{},int{},int{}); std::lerp(float{}, double{}, (long double)0); } https://godbolt.org/z/3PqP9M4GE Current behaviour: Does not compile with: "error: call of overloaded 'lerp(int, int, int)' is ambiguous" and "error: call of overloaded 'lerp(float, double, long double)' is ambiguous". Expected behaviour: Compilation with no issues.
next reply other threads:[~2021-08-12 2:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-12 2:32 konstantinua00 at gmail dot com [this message] 2021-08-12 7:36 ` [Bug libstdc++/101870] " redi at gcc dot gnu.org 2021-08-12 18:46 ` cvs-commit at gcc dot gnu.org 2021-08-12 18:52 ` redi at gcc dot gnu.org 2021-10-12 10:59 ` cvs-commit at gcc dot gnu.org 2021-10-12 11:21 ` redi at gcc dot gnu.org 2021-11-26 15:40 ` cvs-commit at gcc dot gnu.org 2021-11-26 15:45 ` redi at gcc dot gnu.org 2022-05-09 16:40 ` cvs-commit at gcc dot gnu.org 2022-05-09 16:51 ` redi 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-101870-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).