Re: Classinfo and @nogc conflict
On Tuesday, 6 March 2018 at 03:07:49 UTC, solidstate1991 wrote:
I use classinfo for detecting the type of bitmaps, and while I
probably will have a workaround for the associative array stuff
Have you tried `item.classinfo is typeid(xxx)` so `is` instead of
`==`? That... might not work across shared libraries, but
otherwise it should give the same comparison without any string
compare.
but the trickier part would be making the toString function
@nogc (make its return value a ref type?).
There's already options for toString((char[] s) { process s here
} ) that can dump it into a stack buffer. Perhaps the druntime
function could call that overload instead of the zero-arg version
too.
Classinfo and @nogc conflict
I'm trying to speed up my graphic engine, however the presence of the GC in function Layer.updateRaster (see here: https://github.com/ZILtoid1991/pixelperfectengine/blob/master/pixelperfectengine/src/PixelPerfectEngine/graphics/layers.d ) means I get an occasional bump in CPU usage if not a framedrop (most performance related thing got fixed since then). I use classinfo for detecting the type of bitmaps, and while I probably will have a workaround for the associative array stuff, the classinfo thing is embedded into the runtime library, thus it needs to be fixed. I took a look at opEquals, but the trickier part would be making the toString function @nogc (make its return value a ref type?).
