@Defoc ;)
What I think sswift if asking, is why the compiler (Not the code/executable), is letting him compare the "Conceptual" True (or false), with an Int (For example)
What Hes sudjesting isnt away for the code to run differently, but rather a sort of "SuperTypeConverstionStrict", that doesnt allow Type True/False to Type Int
It makes a lot of sence, since
He is right. (Not since the top, but since the thread changed from "This is a bug" to "Could it be done a different way"). It would make more sence to ban non-explicite Int to Bool (Even though we havent got bool, thats what is happening). And then we wouldnt have the problem of
What I think sswift if asking, is why the compiler (Not the code/executable), is letting him compare the "Conceptual" True (or false), with an Int (For example)
What Hes sudjesting isnt away for the code to run differently, but rather a sort of "SuperTypeConverstionStrict", that doesnt allow Type True/False to Type Int
It makes a lot of sence, since
If Xwould still return TRUE or FALSE. And
If (x=10)would still return TRUE. But
If X=Truewould produce an error
He is right. (Not since the top, but since the thread changed from "This is a bug" to "Could it be done a different way"). It would make more sence to ban non-explicite Int to Bool (Even though we havent got bool, thats what is happening). And then we wouldnt have the problem of
X:Int = 10 If X=True ......Being False