atoms: Make destructor explicit to prevent inlining
The GjsAtoms destructor is giant because it calls a JS::Heap destructor for every atom. If it is generated implicitly, then GCC complains about it being too big to inline. Providing an explicit destructor seems to prevent this warning.
Showing with 1 addition and 0 deletions