Avoid seg fault with recent nixpkgs

Resolves #16 (closed) .

I wouldn't say I understand the semantics of C++, but this seems to fix the seg fault. My very cursory understanding is that the previous code was wrong because resp would be deleted when it went out of scope, whereas now it doesn't as it lives on the heap instead. Though this might leak Response values.

What confuses me is why this behaviour changed at all...

changed the description

added 15 commits

• 2ef7c1eb...6671279c - 14 commits from branch ghc:master
• 4974fee4 - Avoid seg fault with new GCC

Compare with previous version

approved this merge request

Yes, this was very wrong previously. Thank you, @teo!

added 2 commits

• 5b4921f5 - 1 commit from branch ghc:master
• 339d1f97 - Avoid seg fault with new GCC

Compare with previous version

enabled an automatic merge when the pipeline for 339d1f97 succeeds

merged