• Harris Hancock's avatar
    Fix crashes due to null vtable pointers with MSVC · 2e7ece6b
    Harris Hancock authored
    MSVC as of VS2015 does not initialize the vtable pointers of constexpr
    objects, causing nullptr dereferences at runtime. To solve this, we can
    just convert them to regular const variables with internal (static)
    linkage.
    
    The internal linkage bit is important: as long as they are invisible
    outside their respective translation units, we do not risk the static
    initialization order fiasco.  If we ever need to reference them outside
    their translation units, we would need to hide them behind functions (like
    HeapArrayDisposer::instance()) to keep things safe.
    2e7ece6b
Name
Last commit
Last update
c++ Loading commit data...
doc Loading commit data...
highlighting Loading commit data...
security-advisories Loading commit data...
.gitignore Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTORS Loading commit data...
LICENSE Loading commit data...
README.md Loading commit data...
RELEASE-PROCESS.md Loading commit data...
appveyor.yml Loading commit data...
mega-test-kenton-home.cfg Loading commit data...
mega-test-kenton-work.cfg Loading commit data...
mega-test-quick.cfg Loading commit data...
mega-test.py Loading commit data...
release.sh Loading commit data...
style-guide.md Loading commit data...
super-test.sh Loading commit data...