disable CGO

[mariomac]

CGO it's not required and usually makes executables more resource-consuming. It also adds some extra requirements to the build/test pipeline (e.g. having to have GCC + libraries, etc...)

Reference read: https://dave.cheney.net/2016/01/18/cgo-is-not-go

[codecov-commenter]

Codecov Report

Merging #318 (0c89d00) into main (8cc4bc7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #318   +/-   ##
=======================================
  Coverage   68.89%   68.89%           
=======================================
  Files          84       84           
  Lines        4900     4900           
=======================================
  Hits         3376     3376           
  Misses       1308     1308           
  Partials      216      216           

Flag	Coverage Δ
unittests	68.89% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[ronensc]

@mariomac thanks for the reference
@KalmanMeth @eranra do you know why CGO_ENABLED=1 was introduced in the first place?

[KalmanMeth]

@ronensc Probably as @mariomac wrote, it is needed for -race.

[mariomac]

Yes, it was needed for -race (didn't know that) so I put it directly in the tests.

However I'm doing few more tests before merging. Despite everybody saying CGo is slower than Go in the internet, I noticed a minor increase in the CPU&Memory consumption 🤷🏻‍♂️