final instance variable can be reassigned to some other value using const in dart












1















Does anyone know why the below code works in dart. final keyword is used to define constant variables. But the below code works little different. If we are using const with a different value it's working fine without giving error.



void main() {
ExampleFinal exampleFinal = new ExampleFinal();
}

class ExampleFinal() {
final a = 5;
ExampleFinal() {
// The below statement will not create any error.
// But if you are remove const in below line it'll show a compile time error.
const a = 6;
print(a); // Prints 6
}
}


Is it a bug or a feature in dart? There is nothing like mentioned in document also.










share|improve this question





























    1















    Does anyone know why the below code works in dart. final keyword is used to define constant variables. But the below code works little different. If we are using const with a different value it's working fine without giving error.



    void main() {
    ExampleFinal exampleFinal = new ExampleFinal();
    }

    class ExampleFinal() {
    final a = 5;
    ExampleFinal() {
    // The below statement will not create any error.
    // But if you are remove const in below line it'll show a compile time error.
    const a = 6;
    print(a); // Prints 6
    }
    }


    Is it a bug or a feature in dart? There is nothing like mentioned in document also.










    share|improve this question



























      1












      1








      1








      Does anyone know why the below code works in dart. final keyword is used to define constant variables. But the below code works little different. If we are using const with a different value it's working fine without giving error.



      void main() {
      ExampleFinal exampleFinal = new ExampleFinal();
      }

      class ExampleFinal() {
      final a = 5;
      ExampleFinal() {
      // The below statement will not create any error.
      // But if you are remove const in below line it'll show a compile time error.
      const a = 6;
      print(a); // Prints 6
      }
      }


      Is it a bug or a feature in dart? There is nothing like mentioned in document also.










      share|improve this question
















      Does anyone know why the below code works in dart. final keyword is used to define constant variables. But the below code works little different. If we are using const with a different value it's working fine without giving error.



      void main() {
      ExampleFinal exampleFinal = new ExampleFinal();
      }

      class ExampleFinal() {
      final a = 5;
      ExampleFinal() {
      // The below statement will not create any error.
      // But if you are remove const in below line it'll show a compile time error.
      const a = 6;
      print(a); // Prints 6
      }
      }


      Is it a bug or a feature in dart? There is nothing like mentioned in document also.







      dart






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 1 at 17:47







      Mahendran Sakkarai

















      asked Jan 1 at 17:45









      Mahendran SakkaraiMahendran Sakkarai

      5,54232956




      5,54232956
























          1 Answer
          1






          active

          oldest

          votes


















          2














          const a = 6;


          creates a new variable that shadows the final a = 5;



          This is possible because {...} creates a new scope in the constructor body.



          If you add at the end of the constructor



          print(this.a); 


          it will print 5






          share|improve this answer
























          • Looks interesting. But it may confuse also. And there is no such thing is mentioned in the document also!

            – Mahendran Sakkarai
            Jan 1 at 18:02






          • 1





            Haven't checked the docs for a while. A type and/or var, const, final before a variable always create a new one. In the same scope you get an error if there are name conflicts. Most languages I worked with behave very similar.

            – Günter Zöchbauer
            Jan 1 at 18:08











          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%2f53997596%2ffinal-instance-variable-can-be-reassigned-to-some-other-value-using-const-in-dar%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









          2














          const a = 6;


          creates a new variable that shadows the final a = 5;



          This is possible because {...} creates a new scope in the constructor body.



          If you add at the end of the constructor



          print(this.a); 


          it will print 5






          share|improve this answer
























          • Looks interesting. But it may confuse also. And there is no such thing is mentioned in the document also!

            – Mahendran Sakkarai
            Jan 1 at 18:02






          • 1





            Haven't checked the docs for a while. A type and/or var, const, final before a variable always create a new one. In the same scope you get an error if there are name conflicts. Most languages I worked with behave very similar.

            – Günter Zöchbauer
            Jan 1 at 18:08
















          2














          const a = 6;


          creates a new variable that shadows the final a = 5;



          This is possible because {...} creates a new scope in the constructor body.



          If you add at the end of the constructor



          print(this.a); 


          it will print 5






          share|improve this answer
























          • Looks interesting. But it may confuse also. And there is no such thing is mentioned in the document also!

            – Mahendran Sakkarai
            Jan 1 at 18:02






          • 1





            Haven't checked the docs for a while. A type and/or var, const, final before a variable always create a new one. In the same scope you get an error if there are name conflicts. Most languages I worked with behave very similar.

            – Günter Zöchbauer
            Jan 1 at 18:08














          2












          2








          2







          const a = 6;


          creates a new variable that shadows the final a = 5;



          This is possible because {...} creates a new scope in the constructor body.



          If you add at the end of the constructor



          print(this.a); 


          it will print 5






          share|improve this answer













          const a = 6;


          creates a new variable that shadows the final a = 5;



          This is possible because {...} creates a new scope in the constructor body.



          If you add at the end of the constructor



          print(this.a); 


          it will print 5







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 1 at 17:47









          Günter ZöchbauerGünter Zöchbauer

          327k69980921




          327k69980921













          • Looks interesting. But it may confuse also. And there is no such thing is mentioned in the document also!

            – Mahendran Sakkarai
            Jan 1 at 18:02






          • 1





            Haven't checked the docs for a while. A type and/or var, const, final before a variable always create a new one. In the same scope you get an error if there are name conflicts. Most languages I worked with behave very similar.

            – Günter Zöchbauer
            Jan 1 at 18:08



















          • Looks interesting. But it may confuse also. And there is no such thing is mentioned in the document also!

            – Mahendran Sakkarai
            Jan 1 at 18:02






          • 1





            Haven't checked the docs for a while. A type and/or var, const, final before a variable always create a new one. In the same scope you get an error if there are name conflicts. Most languages I worked with behave very similar.

            – Günter Zöchbauer
            Jan 1 at 18:08

















          Looks interesting. But it may confuse also. And there is no such thing is mentioned in the document also!

          – Mahendran Sakkarai
          Jan 1 at 18:02





          Looks interesting. But it may confuse also. And there is no such thing is mentioned in the document also!

          – Mahendran Sakkarai
          Jan 1 at 18:02




          1




          1





          Haven't checked the docs for a while. A type and/or var, const, final before a variable always create a new one. In the same scope you get an error if there are name conflicts. Most languages I worked with behave very similar.

          – Günter Zöchbauer
          Jan 1 at 18:08





          Haven't checked the docs for a while. A type and/or var, const, final before a variable always create a new one. In the same scope you get an error if there are name conflicts. Most languages I worked with behave very similar.

          – Günter Zöchbauer
          Jan 1 at 18:08




















          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%2f53997596%2ffinal-instance-variable-can-be-reassigned-to-some-other-value-using-const-in-dar%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

          Monofisismo

          Angular Downloading a file using contenturl with Basic Authentication

          Olmecas