Clément Fournier

Maybe we should just allow `ID("-" ID)*` like before but also add an option to use a string literal? This would circumvent this highlighting issue. The key-value pairs also already...

Related to #657

I am closing this as a duplicate because #657 has more references than this one (eg in todos in the code, and in Github issues)

The problem is that the preamble that contains the `defaultFederateConfig` is generated as a top-level preamble: ``` // c.lf ... preamble {= const defaultFederateConfig: __FederateConfig = { ... } =}...

Interesting... Maybe C should support a type syntax like `token`? Since C doesn't support generics, this doesn't conflict with C syntax itself

I created #1479 to track the C type thing separately. This issue remains about `{=0=}` as a time literal, also see https://github.com/lf-lang/lingua-franca/issues/810#issuecomment-998554028 for more justification

If you do that then you'll probably need an escape hatch to use nightly explicitly in LF. Users could bring in dependencies that require nightly.

Thanks for experimenting with this! > A probably better approach is to use a single arity value, such as "java-16", "java-16-preview", "scala-2.12", etc. where we can have both "java" and...

Hi Aaron, I am thrilled you're proposing this and would very much like PMD to migrate away from using Jorje. As you said, pmd-apex is not as widely usable without...

@rsoesemann So there is consensus about the fact that this a good idea, but I don't want to rush this and immediately start porting rules or so. I think the...