Jesús Lapastora

Results 32 comments of Jesús Lapastora

[9195d71](https://github.com/SerenityOS/jakt/pull/972/commits/9195d712b6006c61c7ea0568fcbe3d9b20abe64a) and other commits related to tests will be reordered when submitting the PR so all commits pass CI.

Some screenshots: ![modified and failed](https://cdn.discordapp.com/attachments/977605897964617771/996050881600573440/unknown.png) ![new files](https://cdn.discordapp.com/attachments/977605897964617771/996051974963343400/unknown.png) ![deleted files](https://cdn.discordapp.com/attachments/977605897964617771/996052095537008700/unknown.png)

Removed the `sh` wraps since this problem also happens on the main branch; therefore it wasn't introduced by this.

Sure, I just put the issue in because there was a PR merged that seemed to work, so that it is known to not work in this case.

A reduced sample: ``` function a(args: [String]) {} function main() { let args = ["1", "2", "3"] a(args) } ```

You can't iterate over a Range but, even if it sounds goofy, the syntax allows it: `(0..2)..(8..3)`. This makes no logical sense, but the parser can be made simpler and...

> Sure, that was my point, too. The question is more if it *should* allow it... I don't feel like prohibiting this explicitly syntax-wise, since it's nature is more specific...

`current_param_is_mutable` is needed in non-static methods for `mutable this`. So probably a `current_param_is_mutable || var_decl.mutable` would work.

the tyepchecker is correct, `dict.set` is void (check runtime.jakt)

Looks like the original issue has been fixed by another commit.