Please sign in to comment.
Workaround value-initialization in MSVC
The syntax splitPoints() should force the compiler to value-initialize the array and because there is no user defined c'tor it falls back on zero-initialization. Unfortunatly this is broken in MSVC compilers, because value initialization for non-POD types is not supported, so left splitPoints un-initialized and add in split() initialization of slavesPositions, that is the only member not already set at split time. This fixes an assert under MSVC when running with more than one thread. Spotted and reported by Jundery. No functional change.
- Loading branch information...