Simple question:
var x = '<%=Request["myvar"]%>' || null;
why does resharper say "Code is heuristically unreachable", When this seems to work just fine?
Asked
Active
Viewed 367 times
0
-
so how come it works? if there is a query parameter, it return the query parameter, if there isnt, it returns null. so it does not always short circuit, does it? – Rafael Herscovici Dec 05 '13 at 14:21
-
I think the `|| null` is unreachable, not the request variable. It will always resolve to at least an empty string. – jessehouwing Dec 05 '13 at 14:26
-
"if there isnt, it returns null." - without wanting to sound patronising, are you talking about `"null"` or `null`, which are different? – AakashM Dec 06 '13 at 13:34
-
it returns 'null' not "null", which i find strange by what was said. – Rafael Herscovici Dec 06 '13 at 21:03
1 Answers
1
You are setting x to a string value so it will never equal null. Therefore the || null is unreachable.
This should help: What does the construct x = x || y mean?
Lauren Rutledge
- 1,195
- 5
- 18
- 27
-
as per my comment, if the string is empty, i do get null. if it was unreachable, why do i get the null result when the string is empty? – Rafael Herscovici Dec 05 '13 at 15:01