Trendlist: 11/10/21

Wednesday, November 10, 2021

Italian Coffee

Ciao coffee lover,

What's in your mug today?

What?? Italian coffee is not really from Italy??

Coffee beans are sourced from all over the world and imported to the country. The main popularity surrounding Italian coffee is the culture of the country.

Italian coffee remains popular today because this was the birthplace of espresso.

Pioneers like Angelo Moriondo, Luigi Bezzera and Desiderio Pavoni developed early versions of the espresso machines that still power up most Starbucks coffee drinks to this day, from the cappuccino to the macchiato.

Italians have many other 'types' of coffee - cappuccino, caffè latte, caffè macchiato, to name a few.

But, if an Italian orders a coffee, they are ordering an espresso.

Coffee culture in Italy hasn't changed much since the third wave of coffee began.

While there are a few third wave coffee bars in some of the bigger cities like Milan and Rome, the majority of Italians are perfectly content with their classic espresso at the neighbourhood bar.

Read more about the land of the espressi:

https://www.batchcoffee.co.uk/stories/italian-coffee

Arrivederci,
Tom
Self-confessed coffee snob (& Head of Coffee)

https://www.batchcoffee.co.uk

Follow us on Facebook
Follow us on Instagram
Follow us on Twitter

Copyright © 2021 Batch Coffee UK, All rights reserved.
You are receiving this email because you opted in via our website.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

[New post] protobuf NPE

Respond to this post by replying above this line

protobuf NPE

by lwpro2

What language does this apply to?
Java

If it's a proto syntax change, is it for proto2 or proto3?
proto3

If it's about generated code change, what programming language?
Java

Describe the problem you are trying to solve.
For the message below,

 message Position {     string portfolio =1; }

The generated setter would be something like this

       public Builder setPortfolio(           java.lang.String value) {         if (value == null) {          throw new NullPointerException();         }            portfolio_ = value;         onChanged();         return this;       }

There is a throw NPE within the method.

I think this is really an opinioned approach, which instead should leave to developers to decide whether to handle it or throw NPE.
There could be a position message, for example, with many known optional field which could be null. Developers should be in a better position on how those fields should be set.

Describe the solution you'd like

The generated class should take the value to be set as it is. Something like

       public Builder setPortfolio(           java.lang.String value) { //        if (value == null) { //         throw new NullPointerException(); //        }            portfolio_ = value;         onChanged();         return this;       }

Describe alternatives you've considered

Additional context
Add any other context or screenshots about the feature request here.

I guess the current "opinioned" approach probably could be due to a constraint from the protobuf format, where an int was used to determine the length-delimited value's length. If no, I think by introducing a negative int (-1) could tell whether the following value is really empty (0) or null (-1).

https://github.com/protocolbuffers/protobuf/issues/9207

lwpro2 | November 10, 2021 at 2:44 pm | Categories: Java | URL: https://wp.me/p1byFS-Cm

Comment