Christian Menard

Thanks for reporting this. Unfortunately, I don't have access to a MacOS device for reproducing the behaviour and testing fixes. Could you check if #1242 fixes the issue and compilation...

@zekailin00 Did you also update all submodules? And do you still have any build artifacts from your earlier tries? You can use `lfc -c ...` to clean all build artifacts...

@petervdonovan could you have a look at this? Is it save to just use `toOriginalText()` here? It looks like the code tagging is breaking things in TypeScript.

> I suggest it be "current logical time," whatever that happens to be, but the handler will also need access to time t. This worries me, as it would certainly...

Right, but at least now we know *when* (in logical time) the handler is invoked. I don't have a better suggestion, but I am a bit concerned about loss of...

I agree with @oowekyala that our current syntax can be described as `state name: type(expr)`, or `state name: type(expr, expr, expr, ...)` for C++ constructors. In this regard, I find...

> How so? I think Swift, Scala, and Rust seem to be using this var name: type = expr type of assignment. I guess it's just me then :). This...

One thing that I am a bit concerned about now, is that the grammar rules assume that `(1, 2, 3)` means a tuple and `[1, 2, 3]` means a list....

Right. I already briefly spoke with @oowekyala about this. I also still have it on my TODO List to create an issue detailing several action items on the way forward....

This is strange. Just out of curiosity: what happens if you now update to gradle 7.4 again? And have you tried to clean first (`.\gradlew clean` or `./bin/build-lfc -c`)? Note...