Thanks for the heads up. Whoever is maintaining those repos (?) need to turn
off issues:
https://help.github.com/en/github/managing-your-work-on-github/disabling-issues
Tor Arne
> On 6 Mar 2020, at 08:48, Samuel Gaist via Development
> wrote:
>
> Hi,
>
> For once, something not strictly
Hmm, maybe we should add README.md to each repo, to direct users to the right
places for bugs and patches.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Will do.
Sorry, didn't see this before,
Marc
-Original Message-
From: "Thiago Macieira"
Sent: 29/02/2020 00:09
To: "development@qt-project.org"
Subject: [Development] Abandoning fix for QTBUG-67970 - QString
::u16string_view support
Task filed by Herb Sutter.
Regarding exceptions, I see your point. Personally I agree with using
exceptions here. If there are no well justified objections, just go for it.
On 3/5/20 4:59 PM, Bogdan Vatra wrote:
Hi,
În ziua de joi, 5 martie 2020, la 17:14:44 EET, Vitaly Fanaskov a scris:
I think something like
Hi Bogdan,
first of all, I think improving the JNI error handling is a great idea.
However, I'm currently not convinced that we should (unconditionally)
require exceptions, or that we really need them. As far as I can tell,
the Android NDK still disables exceptions by default, and the last
>Thanks for the heads up. Whoever is maintaining those repos (?) need to turn
>off issues:
>>https://help.github.com/en/github/managing-your-work-on-github/disabling-issues
I wish this could be done via the parent organization. But there doesn't seem
to be an option for it. Sigh, I guess I
06.03.2020, 14:04, "Alex Blasche" :
>> Thanks for the heads up. Whoever is maintaining those repos (?) need to turn
>> off issues:
>> >https://help.github.com/en/github/managing-your-work-on-github/disabling-issues
>
> I wish this could be done via the parent organization. But there doesn't
Hi,
I think it would be great to have a result type in the Qt API and use that,
instead of C++ exceptions. In theory we could use std::variant, but I think the
API inconvenient for the use-case of a result. That wouldn't prevent us from
using it in the implementation though.
Simon
I fixed all of them up.
--
Alex
From: Samuel Gaist
Sent: Friday, March 06, 2020 14:34
To: Alex Blasche
Cc: Tor Arne Vestbø; development@qt-project.org
Subject: Re: [Development] Github issues
> On 6 Mar 2020, at 12:00, Alex Blasche wrote:
>
>>
> On 6 Mar 2020, at 12:00, Alex Blasche wrote:
>
>> Thanks for the heads up. Whoever is maintaining those repos (?) need to turn
>> off issues:
>> >https://help.github.com/en/github/managing-your-work-on-github/disabling-issues
>
> I wish this could be done via the parent organization. But
06.03.2020, 17:07, "Alex Blasche" :
> I fixed all of them up.
What about setting issue template with warning in case situation repeats in
future?
To do this you create ".github" repository inside organization, and add
ISSUE_TEMPLATE file there.
--
Regards,
Konstantin
On Fri, Mar 06, 2020 at 11:59:32AM +, Simon Hausmann wrote:
>Hi,
>
>I think it would be great to have a result type in the Qt API and use
>that, instead of C++ exceptions. In theory we could use std::variant,
>but I think the API inconvenient for the use-case of a result. That
12 matches
Mail list logo
