Custom getter without return on all paths compiles nevertheless












3















I wrote this code:



var test: String? = null
get() {
field?.also {
return "has value"
}
}


It reaches return only when the field is non-null. Otherwise the body just completes. Nevertheless, this compiles fine and returns null if field is null.



If I change to this:



var test: String? = null
get() {
if (field != null)
return "has value"
}


now the compiler complains that the block body needs a return statement.



Is this some undocumented feature or a bug?










share|improve this question



























    3















    I wrote this code:



    var test: String? = null
    get() {
    field?.also {
    return "has value"
    }
    }


    It reaches return only when the field is non-null. Otherwise the body just completes. Nevertheless, this compiles fine and returns null if field is null.



    If I change to this:



    var test: String? = null
    get() {
    if (field != null)
    return "has value"
    }


    now the compiler complains that the block body needs a return statement.



    Is this some undocumented feature or a bug?










    share|improve this question

























      3












      3








      3


      1






      I wrote this code:



      var test: String? = null
      get() {
      field?.also {
      return "has value"
      }
      }


      It reaches return only when the field is non-null. Otherwise the body just completes. Nevertheless, this compiles fine and returns null if field is null.



      If I change to this:



      var test: String? = null
      get() {
      if (field != null)
      return "has value"
      }


      now the compiler complains that the block body needs a return statement.



      Is this some undocumented feature or a bug?










      share|improve this question














      I wrote this code:



      var test: String? = null
      get() {
      field?.also {
      return "has value"
      }
      }


      It reaches return only when the field is non-null. Otherwise the body just completes. Nevertheless, this compiles fine and returns null if field is null.



      If I change to this:



      var test: String? = null
      get() {
      if (field != null)
      return "has value"
      }


      now the compiler complains that the block body needs a return statement.



      Is this some undocumented feature or a bug?







      kotlin






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 17:21









      Marko TopolnikMarko Topolnik

      146k19196323




      146k19196323
























          1 Answer
          1






          active

          oldest

          votes


















          4














          This is indeed a bug, planned to be fixed in 1.3.20.






          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%2f53286435%2fcustom-getter-without-return-on-all-paths-compiles-nevertheless%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            4














            This is indeed a bug, planned to be fixed in 1.3.20.






            share|improve this answer




























              4














              This is indeed a bug, planned to be fixed in 1.3.20.






              share|improve this answer


























                4












                4








                4







                This is indeed a bug, planned to be fixed in 1.3.20.






                share|improve this answer













                This is indeed a bug, planned to be fixed in 1.3.20.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 13 '18 at 18:14









                yoleyole

                59.2k11147142




                59.2k11147142






























                    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%2f53286435%2fcustom-getter-without-return-on-all-paths-compiles-nevertheless%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

                    Xamarin.iOS Cant Deploy on Iphone

                    Glorious Revolution

                    Dulmage-Mendelsohn matrix decomposition in Python