Pierre-Thomas Meisels
Pierre-Thomas Meisels
> The question to me is: Even if other languages allow it for whatever reason, should we really allow it? > I mean we are quite strict up until now....
I know there is no template issue. But an issue description would be nice.
I aggree with @chippmann proposal. Maybe we can prepare a clean doc for adding other JVM languages support while reworking for `4.0` ?
Can you target `develop` branch please ?
@CedNaru why would we use an engine while generating entry ? Or I did not understood the issue and this is not about entry ?
Thanks for explaination. I was wondering how I would treat these pointers regarding buffer etc, but we'll delay them waiting for value classes. @chippmann should we keep this issue opened...
Maybe you can directly target `master`, as `develop` branch is going to die with `3.5` release.
> > Maybe you can directly target `master`, as `develop` branch is going to die with `3.5` release. > > But isn't this going to be merge beforehand and would...
On my side I do agree with @CedNaru Kotlin first, but I don't think we should close this repo to other JVM languages. Or maybe I'm missing something ?
I agree we should make it as a gradle task, this would be easier for packaging games from CI