You can just modify the current code. I think it's either one of the copyMem, zeroMem functions or the cstring function that triggers this.
Normally the error message when you tag function should give you a hint.
Otherwise you can use this:
{.noSideEffect.}:
mySuspectedSideEffectStatement()
Run
Just bisect the code with the {.noSideEffect.} block until the function
compiles. And then it will be easier to discuss the appropriate step. maybe
it's just doing a `for loop` or doing `reset(foo)`
