Structured binding on constWhat is the difference between const int*, const int * const, and int const *?String literal in templates - different behavior of compilersstructured binding with [[maybe_unused]]Capturing array of vectors in lambda makes elements constExplicit destructor call with decltypeWhy “int & const” compiles fine with MSVC?Discards qualifiers unknown cause (std::bind() / lambda)Visual accept std::string from std::byte iteratorC++17 - Binding rvalue reference to non-const lvalue refShall structured binding to a copy of a const c-array be const?

A social experiment. What is the worst that can happen?

Divine apple island

Folder comparison

Some numbers are more equivalent than others

When quoting, must I also copy hyphens used to divide words that continue on the next line?

Is it possible to use .desktop files to open local pdf files on specific pages with a browser?

We have a love-hate relationship

Melting point of aspirin, contradicting sources

Simulating a probability of 1 of 2^N with less than N random bits

Diode in opposite direction?

What does the Rambam mean when he says that the planets have souls?

Can I rely on this github repository files?

Bob has never been a M before

Has Darkwing Duck ever met Scrooge McDuck?

What is the gram­mat­i­cal term for “‑ed” words like these?

Is XSS in canonical link possible?

What does this horizontal bar at the first measure mean?

Why does Async/Await work properly when the loop is inside the async function and not the other way around?

Flux received by a negative charge

Did US corporations pay demonstrators in the German demonstrations against article 13?

Proving a function is onto where f(x)=|x|.

How to align and center standalone amsmath equations?

Is possible to search in vim history?

Proof of Lemma: Every nonzero integer can be written as a product of primes



Structured binding on const


What is the difference between const int*, const int * const, and int const *?String literal in templates - different behavior of compilersstructured binding with [[maybe_unused]]Capturing array of vectors in lambda makes elements constExplicit destructor call with decltypeWhy “int & const” compiles fine with MSVC?Discards qualifiers unknown cause (std::bind() / lambda)Visual accept std::string from std::byte iteratorC++17 - Binding rvalue reference to non-const lvalue refShall structured binding to a copy of a const c-array be const?













7















Is the following code supposed to compile?



void foo() 
const std::pair<int, int> x = 1, 2;

auto [a, b] = x;

static_assert(std::is_const_v<decltype(a)>);
static_assert(std::is_const_v<decltype(b)>);




  • MSVC says "yes!".


  • GCC says "oh no, man!".


  • Clang says "no way!".


So, is this an MSVC bug?



The standard is not straightforward here (I had a quick look), but considering the rules for auto, I suppose, a and b should be copied discarding cv-qualifier.










share|improve this question


























    7















    Is the following code supposed to compile?



    void foo() 
    const std::pair<int, int> x = 1, 2;

    auto [a, b] = x;

    static_assert(std::is_const_v<decltype(a)>);
    static_assert(std::is_const_v<decltype(b)>);




    • MSVC says "yes!".


    • GCC says "oh no, man!".


    • Clang says "no way!".


    So, is this an MSVC bug?



    The standard is not straightforward here (I had a quick look), but considering the rules for auto, I suppose, a and b should be copied discarding cv-qualifier.










    share|improve this question
























      7












      7








      7








      Is the following code supposed to compile?



      void foo() 
      const std::pair<int, int> x = 1, 2;

      auto [a, b] = x;

      static_assert(std::is_const_v<decltype(a)>);
      static_assert(std::is_const_v<decltype(b)>);




      • MSVC says "yes!".


      • GCC says "oh no, man!".


      • Clang says "no way!".


      So, is this an MSVC bug?



      The standard is not straightforward here (I had a quick look), but considering the rules for auto, I suppose, a and b should be copied discarding cv-qualifier.










      share|improve this question














      Is the following code supposed to compile?



      void foo() 
      const std::pair<int, int> x = 1, 2;

      auto [a, b] = x;

      static_assert(std::is_const_v<decltype(a)>);
      static_assert(std::is_const_v<decltype(b)>);




      • MSVC says "yes!".


      • GCC says "oh no, man!".


      • Clang says "no way!".


      So, is this an MSVC bug?



      The standard is not straightforward here (I had a quick look), but considering the rules for auto, I suppose, a and b should be copied discarding cv-qualifier.







      c++ c++17 structured-bindings






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 6 hours ago









      Biagio FestaBiagio Festa

      5,19321239




      5,19321239






















          2 Answers
          2






          active

          oldest

          votes


















          8















          Is the following code supposed to compile?




          It is not. This is an MSVC bug.



          A structured binding declaration introduces a new name (for specification only), e, that is declared like:



          auto e = x;


          The type of e is called E, and since the initializer is tuple-like, the types of the bindings are given by tuple_element_t<i, E>. In this case E is pair<int, int>, so the two types are just int. The rule for decltype of a structured binding is to give the referenced type, so decltype(a) and decltype(b) are both int.



          The important part here is that a and b (the structured bindings) come from the invented variable (e), and not its initializer (x). e is not const because you just declared it auto. What we're doing is copying x, and then taking bindings into this (non-const) copy.






          share|improve this answer






























            3














            The static assertions should fail (so this would be an MSVC bug I guess). Why? Because it's basically the same as the case of:



            void foo() 
            const int x_1 = 1;
            const int x_2 = 2;

            auto a = x_1;
            auto b = x_2;

            static_assert(std::is_const_v<decltype(a)>);
            static_assert(std::is_const_v<decltype(b)>);



            which does indeed fail on MSVC as well.



            In C++ expression types decay on assignment: the auto sees an int, not a const int. Structured binding simply lets you do more than a single auto binding at a time.






            share|improve this answer
























              Your Answer






              StackExchange.ifUsing("editor", function ()
              StackExchange.using("externalEditor", function ()
              StackExchange.using("snippets", function ()
              StackExchange.snippets.init();
              );
              );
              , "code-snippets");

              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "1"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55329651%2fstructured-binding-on-const%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              8















              Is the following code supposed to compile?




              It is not. This is an MSVC bug.



              A structured binding declaration introduces a new name (for specification only), e, that is declared like:



              auto e = x;


              The type of e is called E, and since the initializer is tuple-like, the types of the bindings are given by tuple_element_t<i, E>. In this case E is pair<int, int>, so the two types are just int. The rule for decltype of a structured binding is to give the referenced type, so decltype(a) and decltype(b) are both int.



              The important part here is that a and b (the structured bindings) come from the invented variable (e), and not its initializer (x). e is not const because you just declared it auto. What we're doing is copying x, and then taking bindings into this (non-const) copy.






              share|improve this answer



























                8















                Is the following code supposed to compile?




                It is not. This is an MSVC bug.



                A structured binding declaration introduces a new name (for specification only), e, that is declared like:



                auto e = x;


                The type of e is called E, and since the initializer is tuple-like, the types of the bindings are given by tuple_element_t<i, E>. In this case E is pair<int, int>, so the two types are just int. The rule for decltype of a structured binding is to give the referenced type, so decltype(a) and decltype(b) are both int.



                The important part here is that a and b (the structured bindings) come from the invented variable (e), and not its initializer (x). e is not const because you just declared it auto. What we're doing is copying x, and then taking bindings into this (non-const) copy.






                share|improve this answer

























                  8












                  8








                  8








                  Is the following code supposed to compile?




                  It is not. This is an MSVC bug.



                  A structured binding declaration introduces a new name (for specification only), e, that is declared like:



                  auto e = x;


                  The type of e is called E, and since the initializer is tuple-like, the types of the bindings are given by tuple_element_t<i, E>. In this case E is pair<int, int>, so the two types are just int. The rule for decltype of a structured binding is to give the referenced type, so decltype(a) and decltype(b) are both int.



                  The important part here is that a and b (the structured bindings) come from the invented variable (e), and not its initializer (x). e is not const because you just declared it auto. What we're doing is copying x, and then taking bindings into this (non-const) copy.






                  share|improve this answer














                  Is the following code supposed to compile?




                  It is not. This is an MSVC bug.



                  A structured binding declaration introduces a new name (for specification only), e, that is declared like:



                  auto e = x;


                  The type of e is called E, and since the initializer is tuple-like, the types of the bindings are given by tuple_element_t<i, E>. In this case E is pair<int, int>, so the two types are just int. The rule for decltype of a structured binding is to give the referenced type, so decltype(a) and decltype(b) are both int.



                  The important part here is that a and b (the structured bindings) come from the invented variable (e), and not its initializer (x). e is not const because you just declared it auto. What we're doing is copying x, and then taking bindings into this (non-const) copy.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 6 hours ago









                  BarryBarry

                  185k21325600




                  185k21325600























                      3














                      The static assertions should fail (so this would be an MSVC bug I guess). Why? Because it's basically the same as the case of:



                      void foo() 
                      const int x_1 = 1;
                      const int x_2 = 2;

                      auto a = x_1;
                      auto b = x_2;

                      static_assert(std::is_const_v<decltype(a)>);
                      static_assert(std::is_const_v<decltype(b)>);



                      which does indeed fail on MSVC as well.



                      In C++ expression types decay on assignment: the auto sees an int, not a const int. Structured binding simply lets you do more than a single auto binding at a time.






                      share|improve this answer





























                        3














                        The static assertions should fail (so this would be an MSVC bug I guess). Why? Because it's basically the same as the case of:



                        void foo() 
                        const int x_1 = 1;
                        const int x_2 = 2;

                        auto a = x_1;
                        auto b = x_2;

                        static_assert(std::is_const_v<decltype(a)>);
                        static_assert(std::is_const_v<decltype(b)>);



                        which does indeed fail on MSVC as well.



                        In C++ expression types decay on assignment: the auto sees an int, not a const int. Structured binding simply lets you do more than a single auto binding at a time.






                        share|improve this answer



























                          3












                          3








                          3







                          The static assertions should fail (so this would be an MSVC bug I guess). Why? Because it's basically the same as the case of:



                          void foo() 
                          const int x_1 = 1;
                          const int x_2 = 2;

                          auto a = x_1;
                          auto b = x_2;

                          static_assert(std::is_const_v<decltype(a)>);
                          static_assert(std::is_const_v<decltype(b)>);



                          which does indeed fail on MSVC as well.



                          In C++ expression types decay on assignment: the auto sees an int, not a const int. Structured binding simply lets you do more than a single auto binding at a time.






                          share|improve this answer















                          The static assertions should fail (so this would be an MSVC bug I guess). Why? Because it's basically the same as the case of:



                          void foo() 
                          const int x_1 = 1;
                          const int x_2 = 2;

                          auto a = x_1;
                          auto b = x_2;

                          static_assert(std::is_const_v<decltype(a)>);
                          static_assert(std::is_const_v<decltype(b)>);



                          which does indeed fail on MSVC as well.



                          In C++ expression types decay on assignment: the auto sees an int, not a const int. Structured binding simply lets you do more than a single auto binding at a time.







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited 6 hours ago

























                          answered 6 hours ago









                          einpoklumeinpoklum

                          36.1k28132260




                          36.1k28132260



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Stack Overflow!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55329651%2fstructured-binding-on-const%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Isabella Eugénie Boyer Biographie | Références | Menu de navigationmodifiermodifier le codeComparator to Compute the Relative Value of a U.S. Dollar Amount – 1774 to Present.

                              Lioubotyn Sommaire Géographie | Histoire | Population | Notes et références | Liens externes | Menu de navigationlubotin.kharkov.uamodifier« Recensements et estimations de la population depuis 1897 »« Office des statistiques d'Ukraine : population au 1er janvier 2010, 2011 et 2012 »« Office des statistiques d'Ukraine : population au 1er janvier 2011, 2012 et 2013 »Informations officiellesCartes topographiquesCarte routièrem

                              Mpande kaSenzangakhona Biographie | Références | Menu de navigationmodifierMpande kaSenzangakhonavoir la liste des auteursm