A typical GC case when stack operations may break your code :)
I worked with strings and I encounter one case (I found it as crash occurs, if that means fun :) ) and is a Qt code like this:
I do understand that was my mistake, and so on, but sometimes GC can make the code much cleaner without working with internals and to see that a variable is given on stack and you have to make a copy to not lose the data. as it deallocates when things get out of scope.
const char *cStr = myQString.toAscii().data();