On Sun, May 10, 2020, 8:18 PM Xeno Amess <xenoam...@gmail.com> wrote:
> Hi. > If you mean this then I will be a +1 instead. > Just, do not convert anything original java code to kotlin, and make sure > pure java user will not be affected. > That shouldn't be necessary. And I don't really mind if you add some kotlin util class dealing with > kotlin things. > > > Isira Seneviratne <isirase...@gmail.com> 于2020年5月10日周日 下午9:33写道： > > > On Sun, May 10, 2020, 6:55 PM Gilles Sadowski <gillese...@gmail.com> > > wrote: > > > > > Hi. > > > > > > In what consists the "porting"? Could you give an example? > > > > > > > Of course. > > > > Extension functions and properties are a language feature of Kotlin, > which > > allow a function/property to be called from a variable as if it was part > of > > the original class declaration: > > https://kotlinlang.org/docs/reference/extensions.html > > > > > > > If it's straightforward and can be automated, it might be worth > > > creating the port for all the Commons components (as part of > > > the release) in a move that can potentially expand our team of > > > developers (if Kotlin programmers are willing to participate to > > > the "upstream" Java project, of course). > > > > > > Regards, > > > Gilles > > > > > > >> [...] > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > >
