Mikolaj Przybylski

Might have fixed that for methods too. I'll test a little bit and push when I'm done

@jntrnr I've added some comments and deleted some debug variables / checks that I forgot about (oops...). Sorry for the mess, it must have been a pain to understand the...

> > we still don't check properly the type of make_memo() > > That has an explicit return type, and is correctly typechecked on main - what fails? Nah, it...

Pushed up the changes. If I remove the `or .get_type(checked_expr.type()) is TypeVariable` on line 3824 in the early return, the only failing test now is generic_across_scopes.jakt with the error ```Error:...

It might not even be related to the `is TypeVariable` early return Am I dumb or is this error getting swallowed? This does not print any Jakt errors and gets...

You learn something everyday  Not sure if this is the way, but I set ignore_errors to `false` before checking for type compatibility in `typecheck_return()` and after the check I...

So is there a bug somewhere? It seems to be set to true both times we call typecheck_return for make_memo

There seems to be a bug for sure. ```cpp function make_memo() throws -> Memo { let x: String = 32 let value: [R:S] = [:] return Memo(value) } ``` Assigning...

It turns out we don't really typecheck functions like make_memo at all currently, so I've removed the hack with setting `.ignore_errors = false`, I don't think it would work in...

Seems to be fixed by https://github.com/SerenityOS/jakt/commit/c213b581ce544d2882d7b13a0e48ae40ad00aeb8