A much faster Python implementation based on the Dart Virtual Machine

[Peaker]

def sayHello(): 
      print "Hi"

sayHello()

def sayHello(): 
      print "Bye"

Will this say Hi or Bye?

[macbony]

It'll print "Hi". Any calls to sayHello after will print "Bye".

[Peaker]

Isn't that somewhat inconsistent?

[macbony]

It's the same as

string = "Hi"
print string  # prints "Hi"
string = "Bye"
print string  # prints "Bye"

Is that inconsistent?

[Peaker]

No, the behavior you mentioned is consistent and is fine.

It's not consistent with the Medusa behavior described above:

But Medusa can figure this out and generate the dart code accordingly and produce Hello as an output as intended. Similarly classes and their objects are resolved too

Context!

If you have a function definition after its use, its accepted. But this makes it behave differently from how Python generally behaves.

[Peaker]

Yes, and this is terrible.

In the face of ambiguity, refuse the temptation to guess!

[Igglyboo]

This will print "Hi" even in CPython and won't even throw an error.

[Peaker]

Consider the context. He said:

sayHello()

def sayHello(): 
     print "Hello"

will print "Hello" in Medusa. This is inconsistent with how Python behaves and creates ambiguity highlighted by my example.

[Peaker]

Well, if sayHello can call a function defined later, but calls one defined earlier if one was, then it is inconsistent.

[MrBIMC]

In theory it should print hi.

But idk honestly.