Just curious:
is there any performance gap using auto instead of int or other
type? For example
int[] ar1 = new int[1000];
auto[] ar2 = new int[1000];
are these equivalent by a perfomance point of view?
Thx
Hi all,
We are currently in the process of building cairo 1.10.2 for windows with the
OpenGL support enabled, for using it in a D program.
This evening (europe time) we probably have succeeded in the build, and
tomorrow we will try some basic test of functionality.
In the meantime, I've found
On 11/24/11 10:09 PM, Trass3r wrote:
Well the runtime performance is equal but of course compilation takes
slightly longer since it has to deduce the type first.
Just curious: I would be surprised if there was actually a measurable
difference between the two – did you ever try to measure it?
The type has to be deduced anyway for type checking the
assignment/initialization.
Makes sense. Overseen that.
But I bet you would waste more memory at compile-time if you had to
type a long template instance name instead of using auto. We're
talkin' bytes here!
Oh wait, I've just remembered I've had a branch in CairoD (the OOP
wrapper) that *did* use GL, so I likely have samples for that as well.
I'll take a look..
OK, it's actually the same samples as the ones using the C API, except
they've been modified to use the OOP CairoD based on a branch that
added OpenGL support.
In short, the link I gave you is the one you want.
On 11/24/11, Andrej Mitrovic andrej.mitrov...@gmail.com wrote:
Oh wait, I've just
This is the nbody benchmark of the Shootout site:
http://shootout.alioth.debian.org/u32/performance.php?test=nbody
The faster version is a Fortran one, probably thanks to vector operations that
allow a better SIMD vectorization.
This is the C++ version:
