Re: [Development] Renaming quint128

2022-11-18 Thread Thiago Macieira
On Friday, 18 November 2022 09:05:51 PST Thiago Macieira wrote: > In fact, I came up with a better solution yesterday after sending this > email: move the support to QUuid. This allows us to have the new (mostly) > source- compatible API in place and simply move the existing QBluetoothUuid > conten

Re: [Development] Renaming quint128

2022-11-18 Thread Thiago Macieira
On Friday, 18 November 2022 04:16:48 PST Shawn Rutledge via Development wrote: > On 2022 Nov 18, at 03:13, Thiago Macieira > mailto:thiago.macie...@intel.com>> wrote: > > I was working on extended integers and added qint128 and quint128 to > > qglobal.h > Interesting. How far can we go with do

Re: [Development] Renaming quint128

2022-11-18 Thread Thiago Macieira
On Friday, 18 November 2022 03:54:46 PST Ivan Solovev via Development wrote: > Hi Thiago, > > > I was working on extended integers and added qint128 and quint128 to > > qglobal.h > (qtypes.h) > > Can you provide a link to your WIP patch? I tried to search but couldn't > find it in gerrit. I hadn

Re: [Development] Renaming quint128

2022-11-18 Thread Shawn Rutledge via Development
On 2022 Nov 18, at 03:13, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: I was working on extended integers and added qint128 and quint128 to qglobal.h Interesting. How far can we go with doubling bits? quint512 in case you have AVX-512 registers? (I must get a laptop with that f

Re: [Development] Renaming quint128

2022-11-18 Thread Ivan Solovev via Development
Hi Thiago, > I was working on extended integers and added qint128 and quint128 to qglobal.h (qtypes.h) Can you provide a link to your WIP patch? I tried to search but couldn't find it in gerrit. > it's used in the API, with a constructor and a toUInt128(), but that's all. It's also not document