if ($bool == true) {
...
}
If ($bool == true) {
Other urls found in this thread:
if (cond != false) {
...
}
if (bool === true ? true : false) {
// do stuff
} else {
// do stuff
}
switch (condition) {
case true:
...
break;
case false:
...
break;
}
The comparison with true here unironically has a purpose due to Javascript being terrible.
yes but if(bool === true) should be sufficient
if("TRUE".equalsIgnoreCase(String.valueOf(bool)) != false) {
if ($condition
holy mother of god
I don't get it
I don't get it
I don't get it
I don't get it
I don't get it
I don't get it
fuck off
HUH?
map
redundant code
instead of doing bool == true, they could just write if(bool)
if (condition=GetHTML('true.com'
if ((this as Window).GetHashCode() == ((((this as object) as Window).GetHashCode()) as object).GetHashCode()) {
Yes but it makes the result faster.
Please tell me that this is a joke and that there is no reason to do this in javascript.
If (integer == 0){
// Do false stuff
} else {
// Do true stuff
}
what
Its not
It is an extra computation that is done to reduce to an expression.
switch is for girls
I don't know what you're talking about. It makes no difference to the compiler. This is purely about readability.
Why do you only care about the compiler?
He give me a dot out.
if (bool == true ? true : false) {
return true;
} else {
return false;
}
I like putting true just for readability.
int i;
i = (cond);
if (1 == i) {
// ...
}
Production-quality code coming through. Move aside peasants. Don't you know if you put the condition in the if kt sometimes doesn't work?
bool ? //do true : //do false;
Explain? If you're evaluating the variable as a Boolean the ternary true : false is useless, obviously.
unless cond can only contain 1 on success it makes no sense
>no default case
But what if neither get hit?
true ? true : false is completely redundant you fucking moron
Sometimes it helps with readability, especially if $bool is badly named or it is a function returning an ok/ko exit value.
retard
>===
is this the power of javascript?
What if you want both to get hit?
based
try:
assert(bool)
# do true stuff
except AssertionError:
# do false stuff
bool means ass in my language lol
Speak American you fucking commie
this is good so you can always have the current boolean for true - in case it changes, code keeps working
>bool
>means
>ASS
>in my language
AHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHHAHHAHAHAHAHAHHAHAHAHAHHAHAHAAHAHAHAHAHAHAHAHAHAHAHA
if (!!cond !== false){
// do stuff
}
LMFAO!!!!
perfectly valid depending on semantics of "cond"
t. reddit
ftg fils de pute
if (condition) {
} else if (!condition) {
} else {
abort();
}
if (1 == !(false)){
//dab really hard
}
Now this is epic
man == orangeMan ? GetAngry() : watchBlackedPorn()
That part is useless obviously, but there is a purpose in doing === true
if (tmp == true && tmp !== true) {
//so stuff
}
[ -z ${cond} ] && # do stuff (inline)
mdrrrrrrrr
this one guy at work always write retarded functions that just return a boolean based on state or something and then it's only ever used once in the render function like
hasToken = () => {
if (this.token) {
return true;
}
return false;
}
render() {
return (
{this.hasToken ? it has a token : null}
)
}
>{this.hasToken ? it has a token : null}
That doesn't even call it lmao
Beautiful
if ∀x(x || !x) {
}
Why is the token a class variable and not in state?
epic victory royale
#DEFINE PI 3;
(and condition (do-things))
if (user.IsJanny)
Dab();
This
has to be said, based and redpilled OP
Functions and variables should be named in such a way that a programmer should be able to infer its general type (number, boolean, string) from the variable name/function signature alone.
...
most of my bools have a "is"/"does"/"has"/"not" in their're names
>>=
this is the power of haskell
if(!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!bool) {
...
}
if((((....(!!!!!!.... bool != !!!!!.... false) != !!!!.... false != .....)))....)
Made me kek thanks