Frotty

They could, but it would require a pretty much complete rewrite of their implementation. Because in Java, enums are basically static instances of a class. In wurst however, the members...

The answer was directed at "why the enum cant be impl like the java enum." Something like your ideas might sound simple, but it actually requires syntax and fundamental changes...

> So yes, enum parameters might come eventually, but it's more likely they will work like in Rust and not like in Java. Since this will likely take a long...

I don't think property would be a good keyword and having scopes directly between variables neither.

what about this @peq ? IIRC the publicread keyword has existed in the grammar for years now, but is unused.

The question would be how to handle older patch support in general. Should be offer build variables or should it just read values from common.j and use existing custom files...

Please see the manual regarding `skip` https://wurstlang.org/manual.html#skip It is not related to loops. Regarding `continue`, we currently aren't planning on adding such a construct. Using continue anywhere else than the...

Those are the "import TypeCasting" warnings ;) I have worked around them by using a function in init that will be removed, but still.

Hey @PhoenixZeng thanks for the reports. Please remember that these are not plugin issues, but the language server which resides in the main repo. wurst4vscode issues must be related to...

> Because this behavior is logically reasonable I would argue that it was a neat hack. Not really logically reasonable to access or modify a member of a class after...