On Thu, Nov 4, 2021 at 9:36 AM Dan Smith <daniel.sm...@oracle.com> wrote:
I guess to rephrase this, I'll just say: yes, there are problems with > int/Integer. But we shouldn't let that tail wag the dog when sorting out > the language model. int/Integer is going to be a special case, no matter > how we stack it. (On the other hand, we really like to look for analogies > from int/Integer when sorting out the language model, and sometimes those > are fruitful. But handle with care.) > Perfectly said, I think. When someone says "so it's like int/Integer?" my hope of being able to answer "yeah actually, that will serve well enough" is closely followed by "we'd like to say yeah, but we *need* to ask you to think of it differently now, but you'll understand why." You probably have that and I'm just delayed in absorbing it. -- Kevin Bourrillion | Java Librarian | Google, Inc. | kev...@google.com
