Seems we have some language features not fully documented (like bitshift operators in #1322).

Would be good to go through language grammar and make sure everything is in the reference guide.

What happened:
Tried running Regression test using command ./test/run_regression_tests.sh $PWD/build.
The test

We use kind for integration tests against a kubernetes cluster. We now have a dirty hack to load the built images into the kind docker daemon since when we started using it kind was at a very early stage and didn't have the load command. Now the load command is available so we can just replace the hack with it!

Docs here
https://kind.sigs.k8s.io/docs/user/quick-start/#loading-an-image-into-y

currently, on every pull request we build a new docker container with all the dependencies from scratch, and rebuild all the code.
If we could cache the go dependencies, and the docker layers, we would save most of the time and resources spent in the CI, the code build itself is not that intensive.
need to look into how to do that with Github Actions

Since the kernel's libbpf seems to handle .text ELF sections gracefully, we should probably do that too.

Can we get some performance comparison between polycube and using standard linux facilities (NAT, iptables, etc.)?

CPU usage, PPS, latencies, etc.