n, this only
applies if someone is actually storing that number or passing it through an
opaque ABI boundary. If instead everything is inline, the compiler's optimiser
should simply emit optimal code.
> But anyway, that's a nice approach, and I should consider using it in my
>
there's any work for
you other than verifying. I was looking for qLess, but we seem to have dropped
it with the std::map rewrite for QMap.
> But then, if we use qt_*() functions, their names will not clash with any
> of the existing APIs, and we can just let the end-users use these
gt; I was not even aware of them, thanks! A brief look at the code shows that
> they shouldn't be affected, but I'll update the Jira ticket to keep them
> in mind.
I wasn't either. I went looking for qLess, which existed for Qt 3, 4 and 5 for
Q(Value)Map, and found them.
plied to Qt6UiPlugin.
We don't understand why it happened there (didn't bother to investigate), so
be aware that your claim may be incorrect and that user code may be affected
regardless of your intention.
See 93de403391b59acf90fbe7319a059382dfe458a6 in the qt-creator repository.
-
then I'd argue such API should
be namespaced with a "q" prefix: qEquals and qCompare (note: we have
QTest::qCompare, but I don't think there's any clash).
> If we advertise only the public API which is not supported by the macros,
> then the users will s
oad the LLVM sources and build it yourself.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ows because it takes too long.
I'm going to switch soon to the UCRT64 build instead.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Developmen
plan on helping fix those issues. So my suggestion is that you
stop trying to build all of Qt. Instead, build ONLY:
1) qtbase (all of it, including the plugins)
2) qttools
Once qdoc is working, you can compile the docs in the modules you want.
--
Thiago Macieira - thiago.macieira (AT)
t thinks they're unclean compared to what the submodule link says they
should be at. Then take action.
> Therefore, I'd like to ask:
> *how to use `init-repository` properly to clean up the working tree after
> checking out?*
You don't. The tool is not designed for tha
screenshots are taken from them.
I didn't realise it was duplicating the screenshots.
Ok, but the information we need isn't there. You need to go into the
submodules Git says have new commits and understand why it thinks that.
--
Thiago Macieira - thiago.macieira (AT) intel.com
C
any images unless what you want to display
is a graphical problem that happened in a graphical Qt application.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Developmen
e
correct commit out?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
successfully completed a dev build
yet. If you wanted that release, you could download the released tarballs,
which are known to work. If you're going to contribute to 6.2, then you need
to first make your contributions to the dev branch.
--
Thiago Macieira - thiago.macieira (AT) intel
conflicting target names between modules on those.
So I repeat: the top-level build is a convenience for developers who are
willing to put in the time to fix the issues found in all of Qt.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engin
On Monday, 21 August 2023 23:34:17 PDT Kai Köhne via Development wrote:
> cmake --build . --parallel 4 --target qminimal qsqlite
As suggested before, I recommend building all of qtbase first. If you're
insisting on the top-level build, then:
ninja qtbase/all
--
Thiago
On Tuesday, 22 August 2023 07:48:53 PDT Haowei Hsu wrote:
> Therefore, I want to
> find a way to switch 'qt/qt5' from a branch/tag to another branch/tag just
> like we do in
> other Git repositories.
Why?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Soft
he exception for
QOperatingSystemVersion for operating systems that have been released since
that Qt release was made.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Developm
fault. I'm not interested in exploring that Git problem. There are other
people and other communication media that can help you with that.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signa
interested in the Git side of the issue. I'd still like to help you
with your problem, but I'm drawing a blank on what you're trying to achieve in
the first place.
There's a difference between your objectives and what you're asking. One is
what you want to accomplish; t
ixed windres.
It looks the latter is not possible, as the bug reports on the topic are still
open:
https://sourceware.org/bugzilla/show_bug.cgi?id=27594
Looks like windres has a design flaw and there's no agreement on how or even if
it should be fixed.
--
Thiago Macieira - thiago.macieira
uting, is yet another level of
indirection. Proof of concept:
https://codereview.qt-project.org/c/qt/qtbase/+/498775
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development ma
all all dependencies for Qt
using pacman. This would remove all the heartache about Strawberry Perl,
PostgreSQL, OpenSSL, MySQL, LLVM, compiler versions. It's one command to
install them all and to later update them.
And if you just want to run qdoc... I believe MSYS2 has a version pre-b
ecure (prevents the
relro functionality), I don't particularly care about this situation. Just
DTRT and turn off lazy binding.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signatu
ine, it isn't imported or exported.
That warning looks like a bug in the compiler instead. So if there's no ill-
effect, I'd just disable and ignore it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Des
nd paid for by the Qt Company, whether that can be supported too.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Friday, 25 August 2023 01:34:17 PDT Hasselmann Mathias via Development
wrote:
> Am 24.08.2023 um 21:42 schrieb Thiago Macieira:
> > That warning looks like a bug in the compiler instead. So if there's no
> > ill- effect, I'd just disable and ignore it.
>
> See
off ASan
* turn on the proper suppressions for ASan
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-proje
t all. I've just added a "return false" to QtNetworkSettings::hasIPv6().
No other OSes should be allowed this exception. This means INTEGRITY and
VxWorks: the former is supported by Qt but not tested in the CI, whereas the
latter is being re-added. They will need to fix the i
the
dynamic symbols of the module in question, not from the debug info. If you
look at the qFatal() leak I fixed, you see that there are unknown QtCore frames
printed, meaning the stack trace didn't use debug symbols.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Softwar
Copyright: it must be held by a legal person. Whether
that person is a physical person (a person person) or a company, trust,
registered association, or organisation, doesn't matter.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineeri
ng an
> app compiled against an older Qt version is just normal, but the other way
> around... definitely not.
Yeah, I think the major/only users of that were ourselves: going up and and
down a release series to test issues.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Ar
ly for
> "silent" test, because the latter calls qFatal, that doesn't seem to happen
> on Linux any more.
Indeed, but that only happens in ASan builds. Anyway, I've submitted changes
to deal with that.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
S
o Qt:
+1 from me
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
asons I can't debug this.
Would be also nice if someone could confirm whether QT_IPC_POSIX was defined in
6.5 for QNX. I expect it was, and the way this is now it's changing
compatibility.
If it was not defined, then we have bigger problems.
--
Thiago Macieira - thiago.macieira (AT)
On Thursday, 14 September 2023 04:42:48 PDT Jörg Bornemann via Development
wrote:
> That's a bug in the condition evaluator (QTBUG-117053), but we can work
> around it: https://codereview.qt-project.org/c/qt/qtbase/+/503980
Thanks, Jörg!
--
Thiago Macieira - thiago.macieira (AT
ive comparison is rare. It's expensive and must be used only
where necessary. And more importantly, it's done ONLY with QString or maybe
its Views, so there's no need to go generic. There's no case-insensitive
comparison of Pixmaps or floating point.
--
Thiago Macieira
acceptable API for it or we'd have to go and change it so it could
be made public.
There's no conclusion in what direction to take in your email. I don't see
anything that would refute my conclusions.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architec
dable by average C++ developers. It is not a good corner of C++.
(4) (the convenience function) is what users expect. Except that we don't need
it to be called qEquals, because we have an even better name for it:
operator==
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Archi
an upgrade to C++20 or complain to their vendors. We are talking about
adding this to a Qt release to happen in 2024, nearly 4 years after the C++
edition was published.
I won't oppose it if it is simple, without imposing undue constraints. But it
need not be part of the initial desi
the macros for public use in the
first place.
> I don't see how we can manage without an API for doing three-way
> comparisons in C++17.
>
> We can try without (4), but (1)-(3) must needs be "semi-public" API (not
> in _p.h's).
I'm ok with semi-public. That
se the configure process called
> find_package(zstd) twice:
>
>1. The 1st time happens when configuring 'qtbase'
>2. The 2nd time happens when configuring 'qttools'
>
> Let's why the 2nd time thinks the 'zstd::libzstd_static' target is
zen 2-week pings I sent over Gerrit; they'll be here
next week if they aren't reviewed.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
"configure.bat" as your email subject said. You ran
the configure shell script. I don't know if that makes a difference, as I
haven't run either for 3 years.
If you want to run configure.bat, you must type:
cmd \ /c ../../configure -release [...]
--
Thiago Macieira - th
Both appear to be import libraries, so I don't know why the linker thinks
there's a conflict.
I repeat that it works for me, but for Haowei it doesn't. I don't know why.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
e root
cause.
That said, it's a good idea to install the mingw64-postgresql package instead
and not depend on C:/Program Files.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic si
d me. I looked
at the CMake output and didn't see anything wrong. The error was in the linker
command-line and I accidentally edited it out when pasting it into the email.
Now that you pointed out, yes, the path to librt.a was wrong.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud
ted without waiting for
all its threads to exit.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ns
may be merged from multiple independent libraries at runtime.
So don't violate ODR.
At worst, you can make them overload each other by having different parameters.
So the Qt functions can switch between the two return type families. But you
can't overload operators, so op
same executable (= cmake
> target).
>
> This is probably the safest. If we allowed this instead, we'd need to
> review all of our APIs to see whether we have a similar issue already.
You must remove "cmake target" portion. This applies to the executable as
loaded into m
mismatches the library, it will fail to
link.
Therefore, "Almost Never Auto" applies and especially so for return types
(when used for deducing a type, not for syntactic brevity).
[1] https://codereview.qt-project.org/c/qt/qtbase/+/491119
--
Thiago Macieira - thiago.macieira (AT)
ped maintain and improve Qt in several aspects, so I have no doubt
that they will do a great job with grpc as maintainers. I've worked with
Alexey more than with Tatiana, but this statement goes for both.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel
t is minimal, because it only
applies to partial ordering, while the vast majority of types are fully
ordered. The impact of QAnyStringView in any API is greater.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Descr
ohc9Wo4
It might be possible to massage the code in such a way that the compiler
realises that it is always idempotent. I haven't managed yet. We can also just
be evil and use bit_cast:
https://gcc.godbolt.org/z/e5zefKevP
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software
thing about changing the function's return type or the layout of the type it
does return.
But yes we should add to it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ordering).
> Which is, probably, already true.
Because the types in the libraries seem to be made so it's very difficult to
get
the actual values into and out of them. But bit_cast throws that away and
allows us to see behind the scenes.
--
Thiago Macieira - thiago.macieira (AT)
On Friday, 10 November 2023 00:11:11 PST Marc Mutz via Development wrote:
> On 09.11.23 16:28, Thiago Macieira wrote:
> > But if the symbols are globally visible (ELF visibility STV_DEFAULT)
>
> That counts as "exported", doesn't it?
Yes.
> Which leaves us with:
is minor thing is worth the hassle. It uglifies our API for
little gain.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Monday, 13 November 2023 09:15:10 PST Marc Mutz via Development wrote:
> On 13.11.23 17:15, Thiago Macieira wrote:
> > On Monday, 13 November 2023 01:34:08 PST Ivan Solovev via Development
wrote:
> > I don't think this minor thing is worth the hassle. It uglifies our AP
On Monday, 13 November 2023 09:38:43 PST Ivan Solovev via Development wrote:
> I really do not want to miss yet another FF.
Given that this is an API that is going to stay with us for at least a decade,
I'd rather get it right than getting it soon.
--
Thiago Macieira - thiago.maci
doesn't have a
> `using std::...`, yet, so we're still ok, and QTestLib doesn't have BC
> constraints).
>
> The Qt::*ordering types, OTOH, are specifically _for_ use in the ABI.
This does mean those types won't be documented, right?
We forward to the C++ Standa
ions.
The ABI functions can return one of these other types:
bool (for equality comparisons)
int (for non-partial ordering)
QPartialOrdering (for partial ordering)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7
id the conversions (specially if we use
> std::bit_cast).
Yes, but the impact only applies to when it needs to translate from out-of-
line to out-of-line. If either side is inline, it'll do the right thing on its
own.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software
pe of any exported function.
So I advise we just use the Qt types and come Qt 7 they become a typedef.
There's no need to use the Standard types right now.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Descr
in this
functionality.
Q: Will you accept if someone else works in fixing these classes or providing a
replacement?
A: Sure. I'll be happy to review your code and offer my insight. I just won't
do the coding myself.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Softwa
;ve had a chance to talk next
week about whether we're going to have a replacement at all or not. If we're
not, if the replacement is simply QFile, then there's nothing stopping us from
deprecating.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect -
on't believe the BIC break between 6.6.0 and 6.6.1 was
> intentional.
It was intentional. We have to choose one of the two ELF versions so we chose
the one that restored compatibility with older 6.x.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DC
Neither QNetworkInterface nor QDBusInterface belong there, therefore there
must be a constraint of some sort.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
D
t than when originally imported. There is no
source- or binary-compatibility guarantee offered against pre-Qt Project or
Labs implementations.
I insist: find a more precise name for the module. "Interface" is too generic,
you need one more word, at a minimum.
--
Thiago Macieira
and who approved it?
That module is not in qt5.git/.gitmodules so it's *not* a Qt module right now.
Source- and binary-compatibility do not apply.
That Git repository is also not sync'ed to GitHub.
Anyway, I am exercising my right to vote to vote -1 on this repository request
s
On Tuesday, 5 December 2023 08:54:29 PST Thiago Macieira wrote:
> Then why are you asking for a repository if it's already there? When was
> that module approved by the Qt Project? I can't find anything in the email
> archives.
>
> The first commit in this repository
broken: while you're trying to get the information about the current item,
it's stat()ing the next. It's also hard to guess which element you're getting
and whether you're accidentally skipping the first entry, or missing the last
one.
All of which are caused by th
t if you have a use for a cross-platform #warning or the deprecation
> of a whole header, restore and stage
> https://codereview.qt-project.org/c/qt/qtbase/+/523363, it's already
> approved and just waits for a user.
QT_WARNING_MSG is useful in other contexts too, for example
That would put OpenSSL 1 support in the same bucket as FreeBSD or HaikuOS or
Sparc processor support: whoever is using this[1] must supply patches.
I propose we re-review once a year.
[1] that may include the Qt Company if their commercial interests call for it.
--
Thiago Macieira - thiago.maciei
that this used to be "GENIVI Extras" does not help yet. "GENIVI
Extras" meant something; "interfaces" or even just "automotive interfaces" do
not.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engine
may come
with existing users may inform us in how much breakage we/they are willing to
accept.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
De
s[2]. There's something wrong with
the build I made yesterday.
[1] https://codebrowser.dev/gcc/gcc/c-family/c-cppbuiltin.cc.html#1224
[2] https://bugreports.qt.io/browse/QTCREATORBUG-30044
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engin
ch to non-strict mode in
compiling those two libraries or we must ignore our own flag in them. Neither
option is appetising.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
De
hould be no behaviour change at
all, anywhere. If that turns out to be a large change, we may want to
postpone; if it breaks something, then we've likely found a bug.
So, +1 for me on going ahead.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Clo
d to know about the classes, enums,
variables, functions, and all other entities declared, which are part of the
translation unit. Moc does need that.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME c
we need from included files, but
we do need something.
In particular, we do need macros themselves, so we can perform proper
expansion in the classes we're trying to generate meta objects for. If this is
something that will never come from imports, great, it's a major barrier
removed.
that predated even me. As far
as I know, that removed the dependency on Perl to compile Qt or to contribute.
What's left that you're seeing?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description:
ipts are entirely optional so their falling into bitrot
is not a problem either.
So if anyone wants to port anything, get busy.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
cripts that
Git itself runs, which happens to include the Gerrit Change-Id one).
So if there are any tools that are considered "should provide"[1] to
beginners, please port them to CMake.
[1] Gradation: "must provide", "should provide", "would be nice
ctor_M_realloc_insert(), which takes the integer by reference, so
the compiler emits an import from the DLL.
This appears to be a GCC bug/shortcoming. Clang and MSVC apparently
automatically emit and export the variable for you:
https://mingw.godbolt.org/z/q4dYdosjh
--
Thiago Maci
On Wednesday, 17 January 2024 19:35:17 PST Thiago Macieira wrote:
> This appears to be a GCC bug/shortcoming. Clang and MSVC apparently
> automatically emit and export the variable for you:
> https://mingw.godbolt.org/z/q4dYdosjh
Reported at https://gcc.gnu.org/bugzilla/show_bug.cgi?
On Wednesday, 17 January 2024 19:35:17 PST Thiago Macieira wrote:
> Alternatives:
> * move to a class that is not exported
>trick: add an empty base with the variable
> * change to enum (if primitive)
* change to an static (inline) constexpr function
Then there's always a
3.5 at
that time, I think it's time to drop.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ugreports.qt.io/browse/QTBUG-109361
> 3. C++20 is mandatory for users of Qt -
> https://bugreports.qt.io/browse/QTBUG-109362
Those tasks haven't got any updates recently. What's the status?
I'd like to ask that we go to #3 for 6.8 or 6.9.
--
Thiago Macieira - thiago.maci
On Tuesday, 2 May 2023 17:39:01 PST Thiago Macieira wrote:
> I don't have access to QNX and INTEGRITY toolchain information, so I'd like
> to request that they simply match the feature list above, with minimal
> workarounds.
What's the current state for those, for suppo
#x27;ve made the change for the non-zero seeds, but one couldn't rely on the
above unless it applied for every seed.f
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Develo
On Sunday, 4 February 2024 06:12:18 PST Giuseppe D'Angelo via Development
wrote:
> Il 03/02/24 22:08, Thiago Macieira ha scritto:
> > But what about a zero seed? It's what we call a "deterministic hashing".
> > We
> > have changed the algorithms on .0 rele
e is.
How about instead we drop at an LTS+2 release? The next one is actually 6.7.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-p
here was no discussion in the change about whether this was
correct or not. It seems I just write it like that.
However, that was qHashBits(). The change I'm talking about is
qHash(QLatin1StringView), specifically so it won't call qHashBits().
--
Thiago Macieira - thiago.macieira (AT
cf742ea23f4a30dcfc38a4988fe56 in 5.3.0.
commit ea8e48a6799cf742ea23f4a30dcfc38a4988fe56
Author: Thiago Macieira
Date: Thu Dec 19 23:32:04 2013 -0800
Update the qHash function for strings to use the CRC32 instruction
According to my profiling of Qt Creator, qHash and the SHA-1 ca
existing users. I have absolutely no problem in making this feature only
accessible in C++20, if need be.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing
On Friday, 9 February 2024 23:04:20 PST Thiago Macieira wrote:
> I added a fallback to C++17. I make no promises that it has the same level
> of compatibility as the C++20 official concept. In fact, I know it doesn't.
> It will reject some types and accept others that it shouldn&
we simply
replace our wording to point to SF22 or am I missing something?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https
rce file in
> an unnamed namespace [...]"
>
> Either I am missunderstanding something, or Qt Coding Conventions and
> C++ Core Guidelines strongly disagree on whether to use anonymous
> namespaces.
Fair.
But I disagree with SF22 and will continue to use statics. There's nothing
wron
can help readability,
> particularly in reviews.
+1
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
--
Development mailing list
Development@qt-project.org
https://lists.qt
name, I guess that just matches the linguistic baggage.)
It's an unnamed namespace, not anonymous namespace.
There's such a thing as anonymous union, though.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Descript
601 - 700 of 6728 matches
Mail list logo
