Why does std::optional::operator=(U&&) require U to be a non-scalar type?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
7
down vote

favorite












For optional's template<class U = T> optional<T>& operator=(U&& v); the standard demands that (see [optional.assign]/3.16):




This function shall not participate in overload resolution unless
...
conjunction_v<is_scalar<T>, is_same<T, decay_t<U>>> is false
...




Why do we have to exclude case when assigning a scalar of type U == T?






c++ language-lawyer c++17 optional







share|improve this question



















  • 3




    probably because then another overload is fine. Looking at a single overload doesnt really give you the full picture
    – user463035818
    4 hours ago














up vote
7
down vote

favorite












For optional's template<class U = T> optional<T>& operator=(U&& v); the standard demands that (see [optional.assign]/3.16):




This function shall not participate in overload resolution unless
...
conjunction_v<is_scalar<T>, is_same<T, decay_t<U>>> is false
...




Why do we have to exclude case when assigning a scalar of type U == T?






c++ language-lawyer c++17 optional







share|improve this question



















  • 3




    probably because then another overload is fine. Looking at a single overload doesnt really give you the full picture
    – user463035818
    4 hours ago












up vote
7
down vote

favorite









up vote
7
down vote

favorite











For optional's template<class U = T> optional<T>& operator=(U&& v); the standard demands that (see [optional.assign]/3.16):




This function shall not participate in overload resolution unless
...
conjunction_v<is_scalar<T>, is_same<T, decay_t<U>>> is false
...




Why do we have to exclude case when assigning a scalar of type U == T?






c++ language-lawyer c++17 optional







share|improve this question















For optional's template<class U = T> optional<T>& operator=(U&& v); the standard demands that (see [optional.assign]/3.16):




This function shall not participate in overload resolution unless
...
conjunction_v<is_scalar<T>, is_same<T, decay_t<U>>> is false
...




Why do we have to exclude case when assigning a scalar of type U == T?






c++ language-lawyer c++17 optional




c++ language-lawyer c++17 optional






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 3 hours ago









Barry

172k18296540




172k18296540










asked 4 hours ago









Zelta

305211




305211







  • 3




    probably because then another overload is fine. Looking at a single overload doesnt really give you the full picture
    – user463035818
    4 hours ago












  • 3




    probably because then another overload is fine. Looking at a single overload doesnt really give you the full picture
    – user463035818
    4 hours ago







3




3




probably because then another overload is fine. Looking at a single overload doesnt really give you the full picture
– user463035818
4 hours ago




probably because then another overload is fine. Looking at a single overload doesnt really give you the full picture
– user463035818
4 hours ago












1 Answer
1






active

oldest

votes

















up vote
12
down vote



accepted










This exists to support:



optional<int> o(42);
o = ; // <== we want this to reset o


We have a bunch of assignment overloads, which take:



  1. nullopt_t

  2. optional const&

  3. optional&&

  4. U&&

  5. optional<U> const&

  6. optional<U>&&

For scalars, specifically, #4 would be a standard conversion whereas anything else would be a user-defined conversion - so it would be the best match. However, the result of that would be assigning o to be engaged with a value of 0. That would mean that o = could potentially mean different things depending on the type of T. Hence, we exclude scalars.



For non-scalars, #4 and #3 would be equivalent (both user-defined conversions), and #3 would win by being a non-template. No problem there.






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',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    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%2f53052395%2fwhy-does-stdoptionaloperator-u-require-u-to-be-a-non-scalar-type%23new-answer', 'question_page');

    );

    Post as a guest

















    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    12
    down vote



    accepted










    This exists to support:



    optional<int> o(42);
    o = ; // <== we want this to reset o


    We have a bunch of assignment overloads, which take:



    1. nullopt_t

    2. optional const&

    3. optional&&

    4. U&&

    5. optional<U> const&

    6. optional<U>&&

    For scalars, specifically, #4 would be a standard conversion whereas anything else would be a user-defined conversion - so it would be the best match. However, the result of that would be assigning o to be engaged with a value of 0. That would mean that o = could potentially mean different things depending on the type of T. Hence, we exclude scalars.



    For non-scalars, #4 and #3 would be equivalent (both user-defined conversions), and #3 would win by being a non-template. No problem there.






    share|improve this answer
























      up vote
      12
      down vote



      accepted










      This exists to support:



      optional<int> o(42);
      o = ; // <== we want this to reset o


      We have a bunch of assignment overloads, which take:



      1. nullopt_t

      2. optional const&

      3. optional&&

      4. U&&

      5. optional<U> const&

      6. optional<U>&&

      For scalars, specifically, #4 would be a standard conversion whereas anything else would be a user-defined conversion - so it would be the best match. However, the result of that would be assigning o to be engaged with a value of 0. That would mean that o = could potentially mean different things depending on the type of T. Hence, we exclude scalars.



      For non-scalars, #4 and #3 would be equivalent (both user-defined conversions), and #3 would win by being a non-template. No problem there.






      share|improve this answer






















        up vote
        12
        down vote



        accepted







        up vote
        12
        down vote



        accepted






        This exists to support:



        optional<int> o(42);
        o = ; // <== we want this to reset o


        We have a bunch of assignment overloads, which take:



        1. nullopt_t

        2. optional const&

        3. optional&&

        4. U&&

        5. optional<U> const&

        6. optional<U>&&

        For scalars, specifically, #4 would be a standard conversion whereas anything else would be a user-defined conversion - so it would be the best match. However, the result of that would be assigning o to be engaged with a value of 0. That would mean that o = could potentially mean different things depending on the type of T. Hence, we exclude scalars.



        For non-scalars, #4 and #3 would be equivalent (both user-defined conversions), and #3 would win by being a non-template. No problem there.






        share|improve this answer












        This exists to support:



        optional<int> o(42);
        o = ; // <== we want this to reset o


        We have a bunch of assignment overloads, which take:



        1. nullopt_t

        2. optional const&

        3. optional&&

        4. U&&

        5. optional<U> const&

        6. optional<U>&&

        For scalars, specifically, #4 would be a standard conversion whereas anything else would be a user-defined conversion - so it would be the best match. However, the result of that would be assigning o to be engaged with a value of 0. That would mean that o = could potentially mean different things depending on the type of T. Hence, we exclude scalars.



        For non-scalars, #4 and #3 would be equivalent (both user-defined conversions), and #3 would win by being a non-template. No problem there.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 3 hours ago









        Barry

        172k18296540




        172k18296540



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53052395%2fwhy-does-stdoptionaloperator-u-require-u-to-be-a-non-scalar-type%23new-answer', 'question_page');

            );

            Post as a guest
































































            Comments

            Post a Comment

            Popular posts from this blog

            Long meetings (6-7 hours a day): Being “babysat” by supervisor

            Image
            Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 31 down vote favorite 4 I hold a PhD in mechanical engineering with a 7 year background in self-guided, self-paced research including 2 years as a graduate level course instructor and a subject matter expert for various engineering projects in a university setting in the United States. For the last 10-11 months, I am working in a research industry in France where my task is to debug C++ spaghetti code written over a period of several years by my current supervisor. It is a team of 2: just I and my supervisor. Diurnally, I am posed with a "bug of the day" to get out of this C++ code. My supervisor generally gives me about 15-30 minutes to solve it and then accosts me about whether or not the task is completed and then rinses and repeats this until the end of the day. Off-late, my supervisor has been holding 6-7 hour long "meetin
            Read more

            Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite Many fantasy worlds have multiple humanoid species (elves, orcs, humans, etc) living in the same world, in addition to that, they often have the ability to interbreed. And I can't help but question their believability... fantasy-races reproduction interspecies-relations share | improve this question edited Aug 9 at 14:46 Michael Kjörling ♦ 21.1k 10 85 161 asked Aug 9 at 13:13 Chlodio 118 6 closed as unclear what you're asking by MichaelK, Gryphon, John, Vincent, Frostfyre Aug 9 at 15:25 Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question. 3 Stack Exchange exist to
            Read more

            Confectionery

            Image
            Prepared foods made with a lot of sugar or other cabohydrates "Sweetmeat" redirects here. For the racehorse, see Sweetmeat (horse). Not to be confused with Sweetbread. This Kransekake is a traditional Scandinavian baker's confection. Confectionery is the art of making confections , which are food items that are rich in sugar and carbohydrates. Exact definitions are difficult. [1] In general, though, confectionery is divided into two broad and somewhat overlapping categories, bakers' confections and sugar confections. [2] Bakers' confectionery, also called flour confections , includes principally sweet pastries, cakes, and similar baked goods. Sugar confectionery includes candies ( sweets in British English), candied nuts, chocolates, chewing gum, bubble gum, pastillage, and other confections that are made primarily of sugar. In some cases, chocolate confections (confections made of chocolate) are treated as a separate category, as are sugar-free versions of
            Read more