Why does indexOf not break?












10















I made a typo in TypeScript which was picked up during code review.



I used someArray.indexOf[someObject] instead of someArray.indexOf(someObject);



I would expect an error from the IDE/Compiler. Instead, no errors were raised and the result was simply undefined.



Can anyone explain this?






javascript angular typescript







share|improve this question

























  • What did you assign the result of? Because what you wrote is valid you are taking the someObject member of the indexOf method. Well, trying to. The only error would come from TypeScript compilation and only if you try to assign the result to something that doesn't match the expected type.

    – vlaz
    59 mins ago






  • 1





    Welcome to javascript, where everything is an object!

    – Jean-Baptiste Yunès
    59 mins ago






  • 2





    @Jean-BaptisteYunès including null...

    – vlaz
    58 mins ago











  • @vlaz sarcasm ?

    – Florian
    44 mins ago






  • 1





    @DeWetvanAs I am actually curious about your problem - this seems like a genuine bug/problem with TypeScript see example here. It seems that if you are trying to assign to a variable of type number, the result of .indexOf[someObject] shouldn't be considered a number and thus the compilation would fail. That's the whole idea of TypeScript is - to enforce the types. The answers here focus on JS but ignore this.

    – vlaz
    10 mins ago
















10















I made a typo in TypeScript which was picked up during code review.



I used someArray.indexOf[someObject] instead of someArray.indexOf(someObject);



I would expect an error from the IDE/Compiler. Instead, no errors were raised and the result was simply undefined.



Can anyone explain this?






javascript angular typescript







share|improve this question

























  • What did you assign the result of? Because what you wrote is valid you are taking the someObject member of the indexOf method. Well, trying to. The only error would come from TypeScript compilation and only if you try to assign the result to something that doesn't match the expected type.

    – vlaz
    59 mins ago






  • 1





    Welcome to javascript, where everything is an object!

    – Jean-Baptiste Yunès
    59 mins ago






  • 2





    @Jean-BaptisteYunès including null...

    – vlaz
    58 mins ago











  • @vlaz sarcasm ?

    – Florian
    44 mins ago






  • 1





    @DeWetvanAs I am actually curious about your problem - this seems like a genuine bug/problem with TypeScript see example here. It seems that if you are trying to assign to a variable of type number, the result of .indexOf[someObject] shouldn't be considered a number and thus the compilation would fail. That's the whole idea of TypeScript is - to enforce the types. The answers here focus on JS but ignore this.

    – vlaz
    10 mins ago














10












10








10








I made a typo in TypeScript which was picked up during code review.



I used someArray.indexOf[someObject] instead of someArray.indexOf(someObject);



I would expect an error from the IDE/Compiler. Instead, no errors were raised and the result was simply undefined.



Can anyone explain this?






javascript angular typescript







share|improve this question
















I made a typo in TypeScript which was picked up during code review.



I used someArray.indexOf[someObject] instead of someArray.indexOf(someObject);



I would expect an error from the IDE/Compiler. Instead, no errors were raised and the result was simply undefined.



Can anyone explain this?






javascript angular typescript




javascript angular typescript






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 53 mins ago







De Wet van As

















asked 1 hour ago









De Wet van AsDe Wet van As

787




787













  • What did you assign the result of? Because what you wrote is valid you are taking the someObject member of the indexOf method. Well, trying to. The only error would come from TypeScript compilation and only if you try to assign the result to something that doesn't match the expected type.

    – vlaz
    59 mins ago






  • 1





    Welcome to javascript, where everything is an object!

    – Jean-Baptiste Yunès
    59 mins ago






  • 2





    @Jean-BaptisteYunès including null...

    – vlaz
    58 mins ago











  • @vlaz sarcasm ?

    – Florian
    44 mins ago






  • 1





    @DeWetvanAs I am actually curious about your problem - this seems like a genuine bug/problem with TypeScript see example here. It seems that if you are trying to assign to a variable of type number, the result of .indexOf[someObject] shouldn't be considered a number and thus the compilation would fail. That's the whole idea of TypeScript is - to enforce the types. The answers here focus on JS but ignore this.

    – vlaz
    10 mins ago



















  • What did you assign the result of? Because what you wrote is valid you are taking the someObject member of the indexOf method. Well, trying to. The only error would come from TypeScript compilation and only if you try to assign the result to something that doesn't match the expected type.

    – vlaz
    59 mins ago






  • 1





    Welcome to javascript, where everything is an object!

    – Jean-Baptiste Yunès
    59 mins ago






  • 2





    @Jean-BaptisteYunès including null...

    – vlaz
    58 mins ago











  • @vlaz sarcasm ?

    – Florian
    44 mins ago






  • 1





    @DeWetvanAs I am actually curious about your problem - this seems like a genuine bug/problem with TypeScript see example here. It seems that if you are trying to assign to a variable of type number, the result of .indexOf[someObject] shouldn't be considered a number and thus the compilation would fail. That's the whole idea of TypeScript is - to enforce the types. The answers here focus on JS but ignore this.

    – vlaz
    10 mins ago

















What did you assign the result of? Because what you wrote is valid you are taking the someObject member of the indexOf method. Well, trying to. The only error would come from TypeScript compilation and only if you try to assign the result to something that doesn't match the expected type.

– vlaz
59 mins ago





What did you assign the result of? Because what you wrote is valid you are taking the someObject member of the indexOf method. Well, trying to. The only error would come from TypeScript compilation and only if you try to assign the result to something that doesn't match the expected type.

– vlaz
59 mins ago




1




1





Welcome to javascript, where everything is an object!

– Jean-Baptiste Yunès
59 mins ago





Welcome to javascript, where everything is an object!

– Jean-Baptiste Yunès
59 mins ago




2




2





@Jean-BaptisteYunès including null...

– vlaz
58 mins ago





@Jean-BaptisteYunès including null...

– vlaz
58 mins ago













@vlaz sarcasm ?

– Florian
44 mins ago





@vlaz sarcasm ?

– Florian
44 mins ago




1




1





@DeWetvanAs I am actually curious about your problem - this seems like a genuine bug/problem with TypeScript see example here. It seems that if you are trying to assign to a variable of type number, the result of .indexOf[someObject] shouldn't be considered a number and thus the compilation would fail. That's the whole idea of TypeScript is - to enforce the types. The answers here focus on JS but ignore this.

– vlaz
10 mins ago





@DeWetvanAs I am actually curious about your problem - this seems like a genuine bug/problem with TypeScript see example here. It seems that if you are trying to assign to a variable of type number, the result of .indexOf[someObject] shouldn't be considered a number and thus the compilation would fail. That's the whole idea of TypeScript is - to enforce the types. The answers here focus on JS but ignore this.

– vlaz
10 mins ago












4 Answers
4






active

oldest

votes


















15














Quite easy.



someArray.indexOf you know that this is a function, which is also an object and can have properties.



By doing someArray.indexOf[someObject], you are trying to reach the property with the key valued to the value of someObject.



Of course, it is not defined on the indexOf function, so it returns undefined.



Quick example that illustrates the syntax and the fact that a function can have properties ;) : 






const array = ;

array.indexOf['anyValue'] = 'test';

console.log(array.indexOf.anyValue);








share|improve this answer



















  • 3





    I think answers here are missing the TypeScript tag. It's entirely reasonable to expect a compilation error in TS. Then again, it depends if you have index: number and index = arr.indexOf[obj] then that should be a compilation error. But index: any wouldn't throw a compilation error.

    – vlaz
    55 mins ago











  • @vlaz +1. sjahan gives OP a quick explanation of the undefined result but the main question remains...

    – Florian
    39 mins ago



















3














Array.indexOf is a function.



Functions are objects.



You were accessing the someObject property of the Array.indexOf function.



You would have got undefined.






const array = [1, 2, 3]

const someObject = 'asdasd'



console.log(array.indexOf[someObject])

// undefined








share|improve this answer



















  • 1





    Array.indexOf is undefined, Array.prototype.indexOf, on the other hand, is a function.

    – Pavlo
    5 mins ago



















0














In short: Because that is the way the language is designed.



JavaScript evaluates an attempt to access a property that doesn't exist as undefined.



It doesn't raise an exception.






share|improve this answer































    0














    Functions in JavaScript are first class objects.



    When you access function Array.indexOf() via bracket notation Array.indexOf['prop'] you actually trying to access a property which does not exist on indexOf so you get undefined.






    share|improve this answer



















    • 1





      What about TypeScript?

      – vlaz
      49 mins ago











    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%2f54254396%2fwhy-does-indexof-not-break%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    15














    Quite easy.



    someArray.indexOf you know that this is a function, which is also an object and can have properties.



    By doing someArray.indexOf[someObject], you are trying to reach the property with the key valued to the value of someObject.



    Of course, it is not defined on the indexOf function, so it returns undefined.



    Quick example that illustrates the syntax and the fact that a function can have properties ;) : 






    const array = ;
    
array.indexOf['anyValue'] = 'test';
    
console.log(array.indexOf.anyValue);








    share|improve this answer



















    • 3





      I think answers here are missing the TypeScript tag. It's entirely reasonable to expect a compilation error in TS. Then again, it depends if you have index: number and index = arr.indexOf[obj] then that should be a compilation error. But index: any wouldn't throw a compilation error.

      – vlaz
      55 mins ago











    • @vlaz +1. sjahan gives OP a quick explanation of the undefined result but the main question remains...

      – Florian
      39 mins ago
















    15














    Quite easy.



    someArray.indexOf you know that this is a function, which is also an object and can have properties.



    By doing someArray.indexOf[someObject], you are trying to reach the property with the key valued to the value of someObject.



    Of course, it is not defined on the indexOf function, so it returns undefined.



    Quick example that illustrates the syntax and the fact that a function can have properties ;) : 






    const array = ;
    
array.indexOf['anyValue'] = 'test';
    
console.log(array.indexOf.anyValue);








    share|improve this answer



















    • 3





      I think answers here are missing the TypeScript tag. It's entirely reasonable to expect a compilation error in TS. Then again, it depends if you have index: number and index = arr.indexOf[obj] then that should be a compilation error. But index: any wouldn't throw a compilation error.

      – vlaz
      55 mins ago











    • @vlaz +1. sjahan gives OP a quick explanation of the undefined result but the main question remains...

      – Florian
      39 mins ago














    15












    15








    15







    Quite easy.



    someArray.indexOf you know that this is a function, which is also an object and can have properties.



    By doing someArray.indexOf[someObject], you are trying to reach the property with the key valued to the value of someObject.



    Of course, it is not defined on the indexOf function, so it returns undefined.



    Quick example that illustrates the syntax and the fact that a function can have properties ;) : 






    const array = ;
    
array.indexOf['anyValue'] = 'test';
    
console.log(array.indexOf.anyValue);








    share|improve this answer













    Quite easy.



    someArray.indexOf you know that this is a function, which is also an object and can have properties.



    By doing someArray.indexOf[someObject], you are trying to reach the property with the key valued to the value of someObject.



    Of course, it is not defined on the indexOf function, so it returns undefined.



    Quick example that illustrates the syntax and the fact that a function can have properties ;) : 






    const array = ;
    
array.indexOf['anyValue'] = 'test';
    
console.log(array.indexOf.anyValue);








    const array = ;
    
array.indexOf['anyValue'] = 'test';
    
console.log(array.indexOf.anyValue);





    const array = ;
    
array.indexOf['anyValue'] = 'test';
    
console.log(array.indexOf.anyValue);






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered 59 mins ago









    sjahansjahan

    3,2051827




    3,2051827








    • 3





      I think answers here are missing the TypeScript tag. It's entirely reasonable to expect a compilation error in TS. Then again, it depends if you have index: number and index = arr.indexOf[obj] then that should be a compilation error. But index: any wouldn't throw a compilation error.

      – vlaz
      55 mins ago











    • @vlaz +1. sjahan gives OP a quick explanation of the undefined result but the main question remains...

      – Florian
      39 mins ago














    • 3





      I think answers here are missing the TypeScript tag. It's entirely reasonable to expect a compilation error in TS. Then again, it depends if you have index: number and index = arr.indexOf[obj] then that should be a compilation error. But index: any wouldn't throw a compilation error.

      – vlaz
      55 mins ago











    • @vlaz +1. sjahan gives OP a quick explanation of the undefined result but the main question remains...

      – Florian
      39 mins ago








    3




    3





    I think answers here are missing the TypeScript tag. It's entirely reasonable to expect a compilation error in TS. Then again, it depends if you have index: number and index = arr.indexOf[obj] then that should be a compilation error. But index: any wouldn't throw a compilation error.

    – vlaz
    55 mins ago





    I think answers here are missing the TypeScript tag. It's entirely reasonable to expect a compilation error in TS. Then again, it depends if you have index: number and index = arr.indexOf[obj] then that should be a compilation error. But index: any wouldn't throw a compilation error.

    – vlaz
    55 mins ago













    @vlaz +1. sjahan gives OP a quick explanation of the undefined result but the main question remains...

    – Florian
    39 mins ago





    @vlaz +1. sjahan gives OP a quick explanation of the undefined result but the main question remains...

    – Florian
    39 mins ago













    3














    Array.indexOf is a function.



    Functions are objects.



    You were accessing the someObject property of the Array.indexOf function.



    You would have got undefined.






    const array = [1, 2, 3]
    
const someObject = 'asdasd'
    

    
console.log(array.indexOf[someObject])
    
// undefined








    share|improve this answer



















    • 1





      Array.indexOf is undefined, Array.prototype.indexOf, on the other hand, is a function.

      – Pavlo
      5 mins ago
















    3














    Array.indexOf is a function.



    Functions are objects.



    You were accessing the someObject property of the Array.indexOf function.



    You would have got undefined.






    const array = [1, 2, 3]
    
const someObject = 'asdasd'
    

    
console.log(array.indexOf[someObject])
    
// undefined








    share|improve this answer



















    • 1





      Array.indexOf is undefined, Array.prototype.indexOf, on the other hand, is a function.

      – Pavlo
      5 mins ago














    3












    3








    3







    Array.indexOf is a function.



    Functions are objects.



    You were accessing the someObject property of the Array.indexOf function.



    You would have got undefined.






    const array = [1, 2, 3]
    
const someObject = 'asdasd'
    

    
console.log(array.indexOf[someObject])
    
// undefined








    share|improve this answer













    Array.indexOf is a function.



    Functions are objects.



    You were accessing the someObject property of the Array.indexOf function.



    You would have got undefined.






    const array = [1, 2, 3]
    
const someObject = 'asdasd'
    

    
console.log(array.indexOf[someObject])
    
// undefined








    const array = [1, 2, 3]
    
const someObject = 'asdasd'
    

    
console.log(array.indexOf[someObject])
    
// undefined





    const array = [1, 2, 3]
    
const someObject = 'asdasd'
    

    
console.log(array.indexOf[someObject])
    
// undefined






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered 59 mins ago









    0xc14m1z0xc14m1z

    1,409512




    1,409512








    • 1





      Array.indexOf is undefined, Array.prototype.indexOf, on the other hand, is a function.

      – Pavlo
      5 mins ago














    • 1





      Array.indexOf is undefined, Array.prototype.indexOf, on the other hand, is a function.

      – Pavlo
      5 mins ago








    1




    1





    Array.indexOf is undefined, Array.prototype.indexOf, on the other hand, is a function.

    – Pavlo
    5 mins ago





    Array.indexOf is undefined, Array.prototype.indexOf, on the other hand, is a function.

    – Pavlo
    5 mins ago











    0














    In short: Because that is the way the language is designed.



    JavaScript evaluates an attempt to access a property that doesn't exist as undefined.



    It doesn't raise an exception.






    share|improve this answer




























      0














      In short: Because that is the way the language is designed.



      JavaScript evaluates an attempt to access a property that doesn't exist as undefined.



      It doesn't raise an exception.






      share|improve this answer


























        0












        0








        0







        In short: Because that is the way the language is designed.



        JavaScript evaluates an attempt to access a property that doesn't exist as undefined.



        It doesn't raise an exception.






        share|improve this answer













        In short: Because that is the way the language is designed.



        JavaScript evaluates an attempt to access a property that doesn't exist as undefined.



        It doesn't raise an exception.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 59 mins ago









        QuentinQuentin

        642k718661036




        642k718661036























            0














            Functions in JavaScript are first class objects.



            When you access function Array.indexOf() via bracket notation Array.indexOf['prop'] you actually trying to access a property which does not exist on indexOf so you get undefined.






            share|improve this answer



















            • 1





              What about TypeScript?

              – vlaz
              49 mins ago
















            0














            Functions in JavaScript are first class objects.



            When you access function Array.indexOf() via bracket notation Array.indexOf['prop'] you actually trying to access a property which does not exist on indexOf so you get undefined.






            share|improve this answer



















            • 1





              What about TypeScript?

              – vlaz
              49 mins ago














            0












            0








            0







            Functions in JavaScript are first class objects.



            When you access function Array.indexOf() via bracket notation Array.indexOf['prop'] you actually trying to access a property which does not exist on indexOf so you get undefined.






            share|improve this answer













            Functions in JavaScript are first class objects.



            When you access function Array.indexOf() via bracket notation Array.indexOf['prop'] you actually trying to access a property which does not exist on indexOf so you get undefined.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 50 mins ago









            GibboKGibboK

            34.3k107317542




            34.3k107317542








            • 1





              What about TypeScript?

              – vlaz
              49 mins ago














            • 1





              What about TypeScript?

              – vlaz
              49 mins ago








            1




            1





            What about TypeScript?

            – vlaz
            49 mins ago





            What about TypeScript?

            – vlaz
            49 mins ago


















            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%2f54254396%2fwhy-does-indexof-not-break%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

            Polycentropodidae

            Image
            Polycentropodidae Plectrocnemia conspersa Siyentipiko nga pagklasipika Ginhadi-an: Animalia Phylum: Arthropoda Ubosphylum: Hexapoda Klase: Insecta Orden: Trichoptera Labawbanay: Hydropsychoidea Banay: Polycentropodidae Binomial nga ngaran Polycentropodidae An Polycentropodidae [1] in uska familia han Insecta. An Polycentropodidae in nahilalakip ha familia nga Hydropsychoidea, ordo nga Trichoptera, classis nga Insecta, punoan nga Arthropoda, ngan regnum nga Animalia. [1] An familia nga Polycentropodidae in naglalakip hin 660 ka mga species, sumala ha Catalogue of Life [1] . An kladograma hini sumala ha Catalogue of Life [1] : Hydropsychoidea   Polycentropodidae  Adectophylax Antillopsyche Cernotina Cyrnellus Cyrnodes Cyrnopsis Cyrnus Eodipseudopsis Eoneureclipsis Holocentropus Kambaitipsyche Neucentropus
            Read more

            Magento 2 Error message: Invalid state change requested

            Image
            2 1 I've created custom Rest API for adding and removing products from cart. I am able to add and delete products from my cart, but when I log in as a customer, I can't add or delete products from cart. API throws message: Invalid state change requested. How can I solve this? magento2 share | improve this question edited Mar 15 '18 at 13:02 Bare Feet 1,561 1 7 32 asked Mar 15 '18 at 12:50 Prabhu M. Prabhu M. 18 5
            Read more

            Paulmy

            Image
            An Paulmy amo in usa ka komyun ha departamento han Indre-et-Loire ngan ha Rehiyon Sentro ha nasod han Fransya. k h l Mga komyun ha departamento han Indre-et-Loire Abilly  · Ambillou  · Amboise  · Anché  · Antogny-le-Tillac  · Artannes-sur-Indre  · Assay  · Athée-sur-Cher  · Autrèche  · Auzouer-en-Touraine  · Avoine  · Avon-les-Roches  · Avrillé-les-Ponceaux  · Azay-le-Rideau  · Azay-sur-Cher  · Azay-sur-Indre  · Ballan-Miré  · Barrou  · Beaulieu-lès-Loches  · Beaumont-en-Véron  · Beaumont-la-Ronce  · Beaumont-Village  · Benais  · Berthenay  · Betz-le-Château  · Bléré  · Bossay-sur-Claise  · Bossée  · Le Boulay  · Bourgueil  · Bournan  · Boussay  · Braslou  · Braye-sous-Faye  · Braye-sur-Maulne  · Brèches  · Bréhémont  · Bridoré  · Brizay  · Bueil-en-Touraine  · Candes-Saint-Martin  · Cangey  · La Celle-Guenand  · La Celle-Saint-Avant  · Céré-la-Ronde  · Cerelles  · Chambon  ·
            Read more