You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some languages have is keyword for various purposes, for example, Python uses it to check the equality between objects and Kotlin uses it to verify if a value appears to a given type.
Considering the ability of time traveling in DreamBerd, maybe it's useful to introduce a variant like was, for example, to check something happened in the past? Similarly, a will be keyword could be exploited to do something in the future.
Not sure I get the example entirely, what's with the await?
I get the idea behind checking if a variable would come into that state in the future, that would be nice.
So a better sample to me would be:
const var score = 5!
if(score will be 10) {
print("You will win!");
}
That would be so useful for making programs:
if(error will be true) {
print("You need to fix your program, back to it!");
}
Basically allowing you to keep working on your program until the above if is never entered, now you know your program is PERFECT! and will never fail!
It would also save us a ton of time as we now never has to write all those pesky tests and even worse, perform them... 😒
Some languages have
is
keyword for various purposes, for example, Python uses it to check the equality between objects and Kotlin uses it to verify if a value appears to a given type.Considering the ability of time traveling in DreamBerd, maybe it's useful to introduce a variant like
was
, for example, to check something happened in the past? Similarly, awill be
keyword could be exploited to do something in the future.Some simple examples:
Meanwhile, other variants like
were
,wasn't
,weren't
,would
orhas been
could also be considered for adding interesting features.The text was updated successfully, but these errors were encountered: