Why is the 'in' operator throwing an error with a string literal instead of logging false?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
As per MDN the in
operator returns true
if the property exists and accordingly the first example logs true. But when using a string literal, why is it throwing an error instead of logging false?
let let1 = new String('test');
console.log(let1.length);
console.log('length' in let1)
var let1 = 'test';
console.log(let1.length);
console.log('length' in let1);
javascript string
add a comment |
As per MDN the in
operator returns true
if the property exists and accordingly the first example logs true. But when using a string literal, why is it throwing an error instead of logging false?
let let1 = new String('test');
console.log(let1.length);
console.log('length' in let1)
var let1 = 'test';
console.log(let1.length);
console.log('length' in let1);
javascript string
I'd assume the temporary wrapper object created for the string is not enumerable ..?
– Teemu
7 hours ago
@Teemu No. There is no temporary wrapper object created at all
– Bergi
7 hours ago
@Bergi Well, that explains a lot.
– Teemu
7 hours ago
add a comment |
As per MDN the in
operator returns true
if the property exists and accordingly the first example logs true. But when using a string literal, why is it throwing an error instead of logging false?
let let1 = new String('test');
console.log(let1.length);
console.log('length' in let1)
var let1 = 'test';
console.log(let1.length);
console.log('length' in let1);
javascript string
As per MDN the in
operator returns true
if the property exists and accordingly the first example logs true. But when using a string literal, why is it throwing an error instead of logging false?
let let1 = new String('test');
console.log(let1.length);
console.log('length' in let1)
var let1 = 'test';
console.log(let1.length);
console.log('length' in let1);
let let1 = new String('test');
console.log(let1.length);
console.log('length' in let1)
let let1 = new String('test');
console.log(let1.length);
console.log('length' in let1)
var let1 = 'test';
console.log(let1.length);
console.log('length' in let1);
var let1 = 'test';
console.log(let1.length);
console.log('length' in let1);
javascript string
javascript string
edited 4 hours ago
Boann
37.4k1290122
37.4k1290122
asked 7 hours ago
brkbrk
29.8k32244
29.8k32244
I'd assume the temporary wrapper object created for the string is not enumerable ..?
– Teemu
7 hours ago
@Teemu No. There is no temporary wrapper object created at all
– Bergi
7 hours ago
@Bergi Well, that explains a lot.
– Teemu
7 hours ago
add a comment |
I'd assume the temporary wrapper object created for the string is not enumerable ..?
– Teemu
7 hours ago
@Teemu No. There is no temporary wrapper object created at all
– Bergi
7 hours ago
@Bergi Well, that explains a lot.
– Teemu
7 hours ago
I'd assume the temporary wrapper object created for the string is not enumerable ..?
– Teemu
7 hours ago
I'd assume the temporary wrapper object created for the string is not enumerable ..?
– Teemu
7 hours ago
@Teemu No. There is no temporary wrapper object created at all
– Bergi
7 hours ago
@Teemu No. There is no temporary wrapper object created at all
– Bergi
7 hours ago
@Bergi Well, that explains a lot.
– Teemu
7 hours ago
@Bergi Well, that explains a lot.
– Teemu
7 hours ago
add a comment |
5 Answers
5
active
oldest
votes
In a sense it is a matter of timing. String literals do not have any properties. The reason that you can call methods and lookup properties on primitive strings is because JavaScript automatically wraps the string primitive in a String
object when a method call or property lookup is attempted. JavaScript does not interpret the in
operator as a method call or property lookup so it does not wrap the primitive in an object and you get an error (because a string primitive is not an object).
See Distinction between string primitives and String objects
Also, the same docs referenced in your question specifically note that using in
on a string primitive will throw an error.
You must specify an object on the right side of the
in
operator. For
example, you can specify a string created with theString
constructor,
but you cannot specify a string literal.
2
This is the shortest and most concise correct answer shown.
– Scott Marcus
7 hours ago
add a comment |
It throws an error because in is an operator for objects:
prop in object
but when you declare a string as ``
(` string literals) or "" ''
(",' string literals) you don't create an object.
Check
typeof new String("x")
("object")
and
typeof `x`
("string").
Those are two different things in JavaScript.
actually my expectation was it will logfalse
instead of throwing error.Actually I was doingif(!(prop in someObj))
– brk
7 hours ago
add a comment |
Because new
creates an Object
and string literal ('') is not an object. and in
operator applicable only to an object instance.
console.log(typeof (new String('ddd')))
console.log(typeof ('ddd'))
add a comment |
typeof('test') == string
(string literal)
typof(new String('test')) == object
(string object)
you can't use in with a string literal.
The in operator returns true if the specified property is in the specified object or its prototype chain.
add a comment |
The in operator can only be used to check if a property is in an
object. You can't search in strings, or in numbers, or other primitive
types.
The first example works and prints 'true' because length
is a property of a string object.
The second example doesn't work and gives you an error because you are trying to look for a property length
in something (a string) that is not an object.
Notice, thatlet1.length
works in the snippet.
– Teemu
7 hours ago
Right. Butlet1
is a string, not an object in the second example.
– VHS
7 hours ago
Umh ... the second example works as well.
– Teemu
7 hours ago
The second example wouldn't work becauselet1
is not an object.
– VHS
7 hours ago
Just run the second snippet, the first console.log shows4
.
– Teemu
7 hours ago
|
show 3 more comments
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55522988%2fwhy-is-the-in-operator-throwing-an-error-with-a-string-literal-instead-of-logg%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
In a sense it is a matter of timing. String literals do not have any properties. The reason that you can call methods and lookup properties on primitive strings is because JavaScript automatically wraps the string primitive in a String
object when a method call or property lookup is attempted. JavaScript does not interpret the in
operator as a method call or property lookup so it does not wrap the primitive in an object and you get an error (because a string primitive is not an object).
See Distinction between string primitives and String objects
Also, the same docs referenced in your question specifically note that using in
on a string primitive will throw an error.
You must specify an object on the right side of the
in
operator. For
example, you can specify a string created with theString
constructor,
but you cannot specify a string literal.
2
This is the shortest and most concise correct answer shown.
– Scott Marcus
7 hours ago
add a comment |
In a sense it is a matter of timing. String literals do not have any properties. The reason that you can call methods and lookup properties on primitive strings is because JavaScript automatically wraps the string primitive in a String
object when a method call or property lookup is attempted. JavaScript does not interpret the in
operator as a method call or property lookup so it does not wrap the primitive in an object and you get an error (because a string primitive is not an object).
See Distinction between string primitives and String objects
Also, the same docs referenced in your question specifically note that using in
on a string primitive will throw an error.
You must specify an object on the right side of the
in
operator. For
example, you can specify a string created with theString
constructor,
but you cannot specify a string literal.
2
This is the shortest and most concise correct answer shown.
– Scott Marcus
7 hours ago
add a comment |
In a sense it is a matter of timing. String literals do not have any properties. The reason that you can call methods and lookup properties on primitive strings is because JavaScript automatically wraps the string primitive in a String
object when a method call or property lookup is attempted. JavaScript does not interpret the in
operator as a method call or property lookup so it does not wrap the primitive in an object and you get an error (because a string primitive is not an object).
See Distinction between string primitives and String objects
Also, the same docs referenced in your question specifically note that using in
on a string primitive will throw an error.
You must specify an object on the right side of the
in
operator. For
example, you can specify a string created with theString
constructor,
but you cannot specify a string literal.
In a sense it is a matter of timing. String literals do not have any properties. The reason that you can call methods and lookup properties on primitive strings is because JavaScript automatically wraps the string primitive in a String
object when a method call or property lookup is attempted. JavaScript does not interpret the in
operator as a method call or property lookup so it does not wrap the primitive in an object and you get an error (because a string primitive is not an object).
See Distinction between string primitives and String objects
Also, the same docs referenced in your question specifically note that using in
on a string primitive will throw an error.
You must specify an object on the right side of the
in
operator. For
example, you can specify a string created with theString
constructor,
but you cannot specify a string literal.
edited 6 hours ago
answered 7 hours ago
benvcbenvc
6,6081828
6,6081828
2
This is the shortest and most concise correct answer shown.
– Scott Marcus
7 hours ago
add a comment |
2
This is the shortest and most concise correct answer shown.
– Scott Marcus
7 hours ago
2
2
This is the shortest and most concise correct answer shown.
– Scott Marcus
7 hours ago
This is the shortest and most concise correct answer shown.
– Scott Marcus
7 hours ago
add a comment |
It throws an error because in is an operator for objects:
prop in object
but when you declare a string as ``
(` string literals) or "" ''
(",' string literals) you don't create an object.
Check
typeof new String("x")
("object")
and
typeof `x`
("string").
Those are two different things in JavaScript.
actually my expectation was it will logfalse
instead of throwing error.Actually I was doingif(!(prop in someObj))
– brk
7 hours ago
add a comment |
It throws an error because in is an operator for objects:
prop in object
but when you declare a string as ``
(` string literals) or "" ''
(",' string literals) you don't create an object.
Check
typeof new String("x")
("object")
and
typeof `x`
("string").
Those are two different things in JavaScript.
actually my expectation was it will logfalse
instead of throwing error.Actually I was doingif(!(prop in someObj))
– brk
7 hours ago
add a comment |
It throws an error because in is an operator for objects:
prop in object
but when you declare a string as ``
(` string literals) or "" ''
(",' string literals) you don't create an object.
Check
typeof new String("x")
("object")
and
typeof `x`
("string").
Those are two different things in JavaScript.
It throws an error because in is an operator for objects:
prop in object
but when you declare a string as ``
(` string literals) or "" ''
(",' string literals) you don't create an object.
Check
typeof new String("x")
("object")
and
typeof `x`
("string").
Those are two different things in JavaScript.
edited 4 hours ago
Boann
37.4k1290122
37.4k1290122
answered 7 hours ago
SkillGGSkillGG
1839
1839
actually my expectation was it will logfalse
instead of throwing error.Actually I was doingif(!(prop in someObj))
– brk
7 hours ago
add a comment |
actually my expectation was it will logfalse
instead of throwing error.Actually I was doingif(!(prop in someObj))
– brk
7 hours ago
actually my expectation was it will log
false
instead of throwing error.Actually I was doing if(!(prop in someObj))
– brk
7 hours ago
actually my expectation was it will log
false
instead of throwing error.Actually I was doing if(!(prop in someObj))
– brk
7 hours ago
add a comment |
Because new
creates an Object
and string literal ('') is not an object. and in
operator applicable only to an object instance.
console.log(typeof (new String('ddd')))
console.log(typeof ('ddd'))
add a comment |
Because new
creates an Object
and string literal ('') is not an object. and in
operator applicable only to an object instance.
console.log(typeof (new String('ddd')))
console.log(typeof ('ddd'))
add a comment |
Because new
creates an Object
and string literal ('') is not an object. and in
operator applicable only to an object instance.
console.log(typeof (new String('ddd')))
console.log(typeof ('ddd'))
Because new
creates an Object
and string literal ('') is not an object. and in
operator applicable only to an object instance.
console.log(typeof (new String('ddd')))
console.log(typeof ('ddd'))
console.log(typeof (new String('ddd')))
console.log(typeof ('ddd'))
console.log(typeof (new String('ddd')))
console.log(typeof ('ddd'))
edited 7 hours ago
answered 7 hours ago
Stranger in the QStranger in the Q
7161618
7161618
add a comment |
add a comment |
typeof('test') == string
(string literal)
typof(new String('test')) == object
(string object)
you can't use in with a string literal.
The in operator returns true if the specified property is in the specified object or its prototype chain.
add a comment |
typeof('test') == string
(string literal)
typof(new String('test')) == object
(string object)
you can't use in with a string literal.
The in operator returns true if the specified property is in the specified object or its prototype chain.
add a comment |
typeof('test') == string
(string literal)
typof(new String('test')) == object
(string object)
you can't use in with a string literal.
The in operator returns true if the specified property is in the specified object or its prototype chain.
typeof('test') == string
(string literal)
typof(new String('test')) == object
(string object)
you can't use in with a string literal.
The in operator returns true if the specified property is in the specified object or its prototype chain.
answered 7 hours ago
FedeScFedeSc
877923
877923
add a comment |
add a comment |
The in operator can only be used to check if a property is in an
object. You can't search in strings, or in numbers, or other primitive
types.
The first example works and prints 'true' because length
is a property of a string object.
The second example doesn't work and gives you an error because you are trying to look for a property length
in something (a string) that is not an object.
Notice, thatlet1.length
works in the snippet.
– Teemu
7 hours ago
Right. Butlet1
is a string, not an object in the second example.
– VHS
7 hours ago
Umh ... the second example works as well.
– Teemu
7 hours ago
The second example wouldn't work becauselet1
is not an object.
– VHS
7 hours ago
Just run the second snippet, the first console.log shows4
.
– Teemu
7 hours ago
|
show 3 more comments
The in operator can only be used to check if a property is in an
object. You can't search in strings, or in numbers, or other primitive
types.
The first example works and prints 'true' because length
is a property of a string object.
The second example doesn't work and gives you an error because you are trying to look for a property length
in something (a string) that is not an object.
Notice, thatlet1.length
works in the snippet.
– Teemu
7 hours ago
Right. Butlet1
is a string, not an object in the second example.
– VHS
7 hours ago
Umh ... the second example works as well.
– Teemu
7 hours ago
The second example wouldn't work becauselet1
is not an object.
– VHS
7 hours ago
Just run the second snippet, the first console.log shows4
.
– Teemu
7 hours ago
|
show 3 more comments
The in operator can only be used to check if a property is in an
object. You can't search in strings, or in numbers, or other primitive
types.
The first example works and prints 'true' because length
is a property of a string object.
The second example doesn't work and gives you an error because you are trying to look for a property length
in something (a string) that is not an object.
The in operator can only be used to check if a property is in an
object. You can't search in strings, or in numbers, or other primitive
types.
The first example works and prints 'true' because length
is a property of a string object.
The second example doesn't work and gives you an error because you are trying to look for a property length
in something (a string) that is not an object.
edited 7 hours ago
answered 7 hours ago
VHSVHS
7,22431128
7,22431128
Notice, thatlet1.length
works in the snippet.
– Teemu
7 hours ago
Right. Butlet1
is a string, not an object in the second example.
– VHS
7 hours ago
Umh ... the second example works as well.
– Teemu
7 hours ago
The second example wouldn't work becauselet1
is not an object.
– VHS
7 hours ago
Just run the second snippet, the first console.log shows4
.
– Teemu
7 hours ago
|
show 3 more comments
Notice, thatlet1.length
works in the snippet.
– Teemu
7 hours ago
Right. Butlet1
is a string, not an object in the second example.
– VHS
7 hours ago
Umh ... the second example works as well.
– Teemu
7 hours ago
The second example wouldn't work becauselet1
is not an object.
– VHS
7 hours ago
Just run the second snippet, the first console.log shows4
.
– Teemu
7 hours ago
Notice, that
let1.length
works in the snippet.– Teemu
7 hours ago
Notice, that
let1.length
works in the snippet.– Teemu
7 hours ago
Right. But
let1
is a string, not an object in the second example.– VHS
7 hours ago
Right. But
let1
is a string, not an object in the second example.– VHS
7 hours ago
Umh ... the second example works as well.
– Teemu
7 hours ago
Umh ... the second example works as well.
– Teemu
7 hours ago
The second example wouldn't work because
let1
is not an object.– VHS
7 hours ago
The second example wouldn't work because
let1
is not an object.– VHS
7 hours ago
Just run the second snippet, the first console.log shows
4
.– Teemu
7 hours ago
Just run the second snippet, the first console.log shows
4
.– Teemu
7 hours ago
|
show 3 more comments
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55522988%2fwhy-is-the-in-operator-throwing-an-error-with-a-string-literal-instead-of-logg%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
I'd assume the temporary wrapper object created for the string is not enumerable ..?
– Teemu
7 hours ago
@Teemu No. There is no temporary wrapper object created at all
– Bergi
7 hours ago
@Bergi Well, that explains a lot.
– Teemu
7 hours ago