Jesús Lapastora

looking at the arguments that the parser got, I've found that the first argument has no name, and that the name is instead the namespace. Makes sense, since we don't...

I reset the pull request so I can rework it from the beginning.

I've made merging this into a git nightmare. I'll start again, basing my branch off `main`.

Merged with module system.

oh okay, thank you. Should we leave this or close this?

Since https://github.com/SerenityOS/jakt/commit/b0b7bddf6015319342418b43dd9c3ad3ce5102bd bare literals are accepted, so looks like this is not an issue anymore

So what you want is something that works in similar way to Haskell's `newtype`? Creating a new type ID but with the same underlying structure?

I'm not sure about the example problem you're proposing: overloading. If you're overloading, shouldn't the argument have different *structure*? I agree with the type "copying" but I would propose a...

I've done this pattern in Rust via a tuple-like struct with a single, unnamed field (which also gets inlined, and you provide the operator impls like a new type). Maybe...

I'm in the process of preventing error propagation on a for loop as well, if this is merged I'll submit another PR.