Kun, I appreciate about your care about Dubbo and you consciousness about things. As you mentioned, it has some additional overhead of having extra object but those are not as big. As Optional or like some other features which gives better redability along with avoiding options where developer could make mistakes and by removing boilerplate code. Along with this, it also make easier for new reader from understanding point of view and increase their confidence or understanding.
As your caring quality and consciousness has brought us this discussion, we should also be keep countinuing of careness by imrpoving our code redability. On Fri, Jan 18, 2019 at 7:34 PM wts <[email protected]> wrote: > I think we should because newer features of a language often have more > good than harm. > > > ------------------ Original ------------------ > From: Kun Song <[email protected]> > Date: Fri,Jan 18,2019 8:05 PM > To: dev <[email protected]> > Subject: Re: [DISCUSS] Should we encourage Optional in Dubbo or not? > > > > Hi community, > > We will support Java 8 since Dubbo 2.7 according to Huxing’s comments > here [1], one big improvement of Java 8 is `Optional`, which is introduced > primarily to avoid `null` and `NullPointerException`. > > `Optional` will make programs more readable and less bug prone, and > some projects such as Apache Pulsar do use `Optional` a lot. However heavy > use of `Optional` may produce many small objects and hence introduce some > performance costs, my question is should we encourage `Optional` in Dubbo? > > Looking forward to hearing from you. > > [1] > https://github.com/apache/incubator-dubbo/issues/3186#issuecomment-454236757 > < > https://github.com/apache/incubator-dubbo/issues/3186#issuecomment-454236757 > >
