[pʲɵs]

Shouldn't actually be all that hard...looks like there are only two major changes: * `finally` handling is now sort of like Java's old `jsr` opcode - need to insert the...

Heh, I looked through the current version of ceval.c and not only `CALL_FINALLY` is about the same as JVM's `jsr`, but it'll share `jsr`'s fate as well: https://bugs.python.org/issue33387

>Seriously: when was the last time you used bit shifting in a high-level language? Well, almost all of my pinned projects use bit shifts, I think? dg itself for what...

Please note that dg is just a small project I made for fun, not something intended for use in anything serious. I didn't even bother telling anyone about it myself,...

I don't know, personally I don't really believe that a fancy syntax is all that important, and the benefits of using a widely known language are unquestionable. Even in Java...

>You mean in dg, right? In both dg and Python. It doesn't matter, code in either results in a `CALL_FUNCTION` opcode or similar. (Inlining would break reflection, etc.) >Did you...

>Maybe, but author _must_ have clarified this in 2 years. You're awfully generous in assuming that the author is good at writing documentation...

Yeah, the tutorial is supposed to be a bit tongue-in-cheek, as the fake O'Reilly cover might suggest. Kind of hints that the project is not particularly serious, no? (Probably didn't...

Hm, it seems the parser consumes the next token after `@` to form some weird construct where `@` is called with the line break operator as an argument.

It does work with keyword arguments. Your example doesn't work because `a: b |>.c` is `(a: b).c`. (Which, I guess, makes passing keyword arguments on separate lines not particularly useful...)