Blamed location is wrong when return type annotation is violated #15

[CodeSteak]

closes #15

Extra function calls are inserted in the AST. If a "return"-location is searched, and the last return was triggered inside of the function that causes the violation, the location of the return is used.

Also the formatting of location has been changed. Now a Location is a "single line". When printing the 2 surrounding lines are also shown.

def foo(flag: bool) -> int:
    print('Hello World')
    if flag:
        return 1
    else:
        return 'you stupid'

foo(False)

outputs

declared at: test-data/testTypesReturn.py:1
  1 > def foo(flag: bool) -> int:
  2 |     print('Hello World')
  3 |     if flag:
  4 |         return 1
  5 |     else:

caused by: test-data/testTypesReturn.py:6
  4 |         return 1
  5 |     else:
  6 >         return 'you stupid'
  7 | 
  8 | foo(False)

[skogsbaer]

Great!