On Friday, 7 February 2014 at 07:43:05 UTC, Steve Teale wrote:
I was attempting to to build my app COMPO using a Makefile this
morning, and at first this worked to some extent, but after
some fiddling with compiler flags to make a release version
that then had problems, I reverted to my
On Thursday, 6 February 2014 at 22:16:30 UTC, Dicebot wrote:
On Thursday, 6 February 2014 at 19:01:52 UTC, Brad Anderson
wrote:
Couldn't scope allocating a class on the stack just be
considered an optimization that can be applied if the scope
storage class become fully implemented?
I think
On Friday, 7 February 2014 at 04:03:58 UTC, Marco Leise wrote:
Am Mon, 03 Feb 2014 22:01:14 +
schrieb Stanislav Blinov stanislav.bli...@gmail.com:
Return-by-value being optimized as a move might be one more
reason why you would like to use slices...
3 doubles is only one machine word
Hi all,
I've been trying to learn more about how the shared qualifier
works, and so far I haven't been able to find much. I've read the
Migrating to Shared article, as well as the shared section in
Attributes, but neither really give a good explanation on the
details of what should be shared
On Friday, 7 February 2014 at 10:50:49 UTC, Stanislav Blinov
wrote:
I know. I also know that people making games are obsessed with
performance :)
And, where there's 3d vector, there would also be 4d vector and
matrices...
Wouldn't it make more sense to aim for a float SIMD
implementation
On Friday, 7 February 2014 at 21:37:26 UTC, Casper Færgemand
wrote:
On Friday, 7 February 2014 at 10:50:49 UTC, Stanislav Blinov
wrote:
I know. I also know that people making games are obsessed with
performance :)
And, where there's 3d vector, there would also be 4d vector
and matrices...
Suppose I have a multi client broadcast server. One client sends
a string, every client receives it. The client read thread reads
the input from the client into a static byte array, makes a copy
and casts it to a string, and passes it to the host thread, which
relays it to all client write
To me it seems that you have to have at least one allocation per
string received.
To submit your string to another thread verbatim, you have to be
able to guarantee that the buffer is immutable, which you cannot
do because you can receive a new string at any given time (which
would overwrite
