Hi All,
I recently stumbled upon an issue where using iterators of a QLinkedList,
altered the "copy" of another QLinkedList.
On reading the iterator docs, I came across this limitation of Qt
containers with implicit sharing:
http://doc.qt.io/qt-5/containers.html#implicit-sharing-iterator-problem
Like I promised, here's a 5 minutes long documentary on BB++:
https://youtu.be/vXmddU_FS30
Regards,
-Phil
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On 07/30/2017 01:23 PM, Phil Bouchard wrote:
I'll generate documentation for your convenience soon.
Like I promised, here's a 5 minutes long documentary:
https://youtu.be/vXmddU_FS30
Regards,
-Phil
___
Development mailing list
Development@qt-proje
Thanks for the information; I already sent this information to Google, Uber
and NASA. I'm about to tell WebKit as well. We'll see what they have to
say.
As far as closures are concerned, there is a way to convert closures with
parameters and return values so I personally don't think it's worth pay
I would suggest you to make your language feature complete before making
any benchmark.
For your information, lambda and variable capture cannot be discussed, it
is absolutely needed.
in my opinion, you totally under estimate the design of a language, please
read on Stroustrup / c++ etc.
as a fir
On 07/21/2017 12:22 AM, Phil Bouchard wrote:
Greetings,
I am now using C++14 standards, the error reporting is all compile-time
now and I get a test that is 3.5 faster than Node.JS! You can see it by
yourselves here:
https://github.com/philippeb8/root_ptr/tree/bb++/bbpp2cpp
I just tried it
