Type-Constrained Optional Extension visible to other types












2















So because I got bored of having to manually nil-coalesce optional values, I decided to make the common default values into nice and easy-to-use extensions on Optional, as seen below:



public extension Optional {
var exists: Bool { return self != nil }
}

public extension Optional where Wrapped == String {
var orEmpty: Wrapped { return self ?? "" }
}

public extension Optional where Wrapped == Int {
var orZero: Wrapped { return self ?? 0 }
}

public extension Optional where Wrapped == Double {
var orZero: Wrapped { return self ?? 0 }
}

public extension Optional where Wrapped == Float {
var orZero: Wrapped { return self ?? 0 }
}

public extension Optional where Wrapped == Bool {
var orFalse: Wrapped { return self ?? false }
}


My issue arrives when attempting to use these on an optional value with a specific type.

I can call .orZero on a variable of type String? and get one of the following errors:




Ambiguous reference to member 'orZero'

'String?' is not convertible to 'Optional'




I'd like to know why Xcode is providing the .orZero properties of such an optional as valid auto-completion options? I would've thought the generic constraints would prevent me from being able to see them.
For what it's worth, I'm using Xcode 10.1, and Swift 4.2










share|improve this question





























    2















    So because I got bored of having to manually nil-coalesce optional values, I decided to make the common default values into nice and easy-to-use extensions on Optional, as seen below:



    public extension Optional {
    var exists: Bool { return self != nil }
    }

    public extension Optional where Wrapped == String {
    var orEmpty: Wrapped { return self ?? "" }
    }

    public extension Optional where Wrapped == Int {
    var orZero: Wrapped { return self ?? 0 }
    }

    public extension Optional where Wrapped == Double {
    var orZero: Wrapped { return self ?? 0 }
    }

    public extension Optional where Wrapped == Float {
    var orZero: Wrapped { return self ?? 0 }
    }

    public extension Optional where Wrapped == Bool {
    var orFalse: Wrapped { return self ?? false }
    }


    My issue arrives when attempting to use these on an optional value with a specific type.

    I can call .orZero on a variable of type String? and get one of the following errors:




    Ambiguous reference to member 'orZero'

    'String?' is not convertible to 'Optional'




    I'd like to know why Xcode is providing the .orZero properties of such an optional as valid auto-completion options? I would've thought the generic constraints would prevent me from being able to see them.
    For what it's worth, I'm using Xcode 10.1, and Swift 4.2










    share|improve this question



























      2












      2








      2








      So because I got bored of having to manually nil-coalesce optional values, I decided to make the common default values into nice and easy-to-use extensions on Optional, as seen below:



      public extension Optional {
      var exists: Bool { return self != nil }
      }

      public extension Optional where Wrapped == String {
      var orEmpty: Wrapped { return self ?? "" }
      }

      public extension Optional where Wrapped == Int {
      var orZero: Wrapped { return self ?? 0 }
      }

      public extension Optional where Wrapped == Double {
      var orZero: Wrapped { return self ?? 0 }
      }

      public extension Optional where Wrapped == Float {
      var orZero: Wrapped { return self ?? 0 }
      }

      public extension Optional where Wrapped == Bool {
      var orFalse: Wrapped { return self ?? false }
      }


      My issue arrives when attempting to use these on an optional value with a specific type.

      I can call .orZero on a variable of type String? and get one of the following errors:




      Ambiguous reference to member 'orZero'

      'String?' is not convertible to 'Optional'




      I'd like to know why Xcode is providing the .orZero properties of such an optional as valid auto-completion options? I would've thought the generic constraints would prevent me from being able to see them.
      For what it's worth, I'm using Xcode 10.1, and Swift 4.2










      share|improve this question
















      So because I got bored of having to manually nil-coalesce optional values, I decided to make the common default values into nice and easy-to-use extensions on Optional, as seen below:



      public extension Optional {
      var exists: Bool { return self != nil }
      }

      public extension Optional where Wrapped == String {
      var orEmpty: Wrapped { return self ?? "" }
      }

      public extension Optional where Wrapped == Int {
      var orZero: Wrapped { return self ?? 0 }
      }

      public extension Optional where Wrapped == Double {
      var orZero: Wrapped { return self ?? 0 }
      }

      public extension Optional where Wrapped == Float {
      var orZero: Wrapped { return self ?? 0 }
      }

      public extension Optional where Wrapped == Bool {
      var orFalse: Wrapped { return self ?? false }
      }


      My issue arrives when attempting to use these on an optional value with a specific type.

      I can call .orZero on a variable of type String? and get one of the following errors:




      Ambiguous reference to member 'orZero'

      'String?' is not convertible to 'Optional'




      I'd like to know why Xcode is providing the .orZero properties of such an optional as valid auto-completion options? I would've thought the generic constraints would prevent me from being able to see them.
      For what it's worth, I'm using Xcode 10.1, and Swift 4.2







      swift generics optional






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 22 '18 at 14:09









      Randika Vishman

      4,68723957




      4,68723957










      asked Nov 20 '18 at 11:09









      royalmurderroyalmurder

      12910




      12910
























          2 Answers
          2






          active

          oldest

          votes


















          1














          .orZero being provided as an auto-completion is a bug. It can be circumvented by rewriting your extensions in terms of the appropriate literal protocols.



          public extension Optional where Wrapped: ExpressibleByIntegerLiteral {
          var orZero: Wrapped { return self ?? 0 }
          }

          public extension Optional where Wrapped: ExpressibleByBooleanLiteral {
          var orFalse: Wrapped { return self ?? false }
          }


          Expressed in this way, Swift can now figure out that .isZero ought not to be suggested for i.e. a variable of type String?, and if you try to call it anyway, it will give the error Type 'String' does not conform to protocol 'ExpressibleByIntegerLiteral'.






          share|improve this answer

































            -1














            Take a look at this.



            In you extension .orZero is only for Int, Float, Double.



            For String you have .orEmpty.






            share|improve this answer
























            • Thanks for the response, Deryck! I'm aware of the type limitations of the optional extensions above. My question is regarding why Xcode presents the wrong properties to me as autocompletion suggestions. I will update the question to outline this more obliquely.

              – royalmurder
              Nov 20 '18 at 11:41











            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%2f53391691%2ftype-constrained-optional-extension-visible-to-other-types%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









            1














            .orZero being provided as an auto-completion is a bug. It can be circumvented by rewriting your extensions in terms of the appropriate literal protocols.



            public extension Optional where Wrapped: ExpressibleByIntegerLiteral {
            var orZero: Wrapped { return self ?? 0 }
            }

            public extension Optional where Wrapped: ExpressibleByBooleanLiteral {
            var orFalse: Wrapped { return self ?? false }
            }


            Expressed in this way, Swift can now figure out that .isZero ought not to be suggested for i.e. a variable of type String?, and if you try to call it anyway, it will give the error Type 'String' does not conform to protocol 'ExpressibleByIntegerLiteral'.






            share|improve this answer






























              1














              .orZero being provided as an auto-completion is a bug. It can be circumvented by rewriting your extensions in terms of the appropriate literal protocols.



              public extension Optional where Wrapped: ExpressibleByIntegerLiteral {
              var orZero: Wrapped { return self ?? 0 }
              }

              public extension Optional where Wrapped: ExpressibleByBooleanLiteral {
              var orFalse: Wrapped { return self ?? false }
              }


              Expressed in this way, Swift can now figure out that .isZero ought not to be suggested for i.e. a variable of type String?, and if you try to call it anyway, it will give the error Type 'String' does not conform to protocol 'ExpressibleByIntegerLiteral'.






              share|improve this answer




























                1












                1








                1







                .orZero being provided as an auto-completion is a bug. It can be circumvented by rewriting your extensions in terms of the appropriate literal protocols.



                public extension Optional where Wrapped: ExpressibleByIntegerLiteral {
                var orZero: Wrapped { return self ?? 0 }
                }

                public extension Optional where Wrapped: ExpressibleByBooleanLiteral {
                var orFalse: Wrapped { return self ?? false }
                }


                Expressed in this way, Swift can now figure out that .isZero ought not to be suggested for i.e. a variable of type String?, and if you try to call it anyway, it will give the error Type 'String' does not conform to protocol 'ExpressibleByIntegerLiteral'.






                share|improve this answer















                .orZero being provided as an auto-completion is a bug. It can be circumvented by rewriting your extensions in terms of the appropriate literal protocols.



                public extension Optional where Wrapped: ExpressibleByIntegerLiteral {
                var orZero: Wrapped { return self ?? 0 }
                }

                public extension Optional where Wrapped: ExpressibleByBooleanLiteral {
                var orFalse: Wrapped { return self ?? false }
                }


                Expressed in this way, Swift can now figure out that .isZero ought not to be suggested for i.e. a variable of type String?, and if you try to call it anyway, it will give the error Type 'String' does not conform to protocol 'ExpressibleByIntegerLiteral'.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 22 '18 at 14:15

























                answered Nov 22 '18 at 14:01









                Marcel TeschMarcel Tesch

                237211




                237211

























                    -1














                    Take a look at this.



                    In you extension .orZero is only for Int, Float, Double.



                    For String you have .orEmpty.






                    share|improve this answer
























                    • Thanks for the response, Deryck! I'm aware of the type limitations of the optional extensions above. My question is regarding why Xcode presents the wrong properties to me as autocompletion suggestions. I will update the question to outline this more obliquely.

                      – royalmurder
                      Nov 20 '18 at 11:41
















                    -1














                    Take a look at this.



                    In you extension .orZero is only for Int, Float, Double.



                    For String you have .orEmpty.






                    share|improve this answer
























                    • Thanks for the response, Deryck! I'm aware of the type limitations of the optional extensions above. My question is regarding why Xcode presents the wrong properties to me as autocompletion suggestions. I will update the question to outline this more obliquely.

                      – royalmurder
                      Nov 20 '18 at 11:41














                    -1












                    -1








                    -1







                    Take a look at this.



                    In you extension .orZero is only for Int, Float, Double.



                    For String you have .orEmpty.






                    share|improve this answer













                    Take a look at this.



                    In you extension .orZero is only for Int, Float, Double.



                    For String you have .orEmpty.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Nov 20 '18 at 11:22









                    Deryck LucianDeryck Lucian

                    1558




                    1558













                    • Thanks for the response, Deryck! I'm aware of the type limitations of the optional extensions above. My question is regarding why Xcode presents the wrong properties to me as autocompletion suggestions. I will update the question to outline this more obliquely.

                      – royalmurder
                      Nov 20 '18 at 11:41



















                    • Thanks for the response, Deryck! I'm aware of the type limitations of the optional extensions above. My question is regarding why Xcode presents the wrong properties to me as autocompletion suggestions. I will update the question to outline this more obliquely.

                      – royalmurder
                      Nov 20 '18 at 11:41

















                    Thanks for the response, Deryck! I'm aware of the type limitations of the optional extensions above. My question is regarding why Xcode presents the wrong properties to me as autocompletion suggestions. I will update the question to outline this more obliquely.

                    – royalmurder
                    Nov 20 '18 at 11:41





                    Thanks for the response, Deryck! I'm aware of the type limitations of the optional extensions above. My question is regarding why Xcode presents the wrong properties to me as autocompletion suggestions. I will update the question to outline this more obliquely.

                    – royalmurder
                    Nov 20 '18 at 11:41


















                    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%2f53391691%2ftype-constrained-optional-extension-visible-to-other-types%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

                    Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

                    ComboBox Display Member on multiple fields

                    Is it possible to collect Nectar points via Trainline?