Fix unsafe pointer

[grongor]

Description

The issue seems valid, the provided solution seems correct, so...I just made the commits. 😆

• Fixes Mocks don't correctly reference unsafe.Pointer #429

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Version of Golang used when building/testing:

• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18

How Has This Been Tested?

Added test so the issue is reproducible.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[codecov-commenter]

Codecov Report

Merging #460 (989253d) into master (9f67b8a) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #460      +/-   ##
==========================================
+ Coverage   70.99%   71.06%   +0.06%     
==========================================
  Files           7        7              
  Lines        1293     1296       +3     
==========================================
+ Hits          918      921       +3     
  Misses        321      321              
  Partials       54       54              

Impacted Files	Coverage Δ
pkg/generator.go	91.51% <100.00%> (+0.04%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f67b8a...989253d. Read the comment docs.