ziglang

Sooner or later we will need to add tests to check for regressions.

I propose the following three kinds of tests:

• Function unit tests (mainly for the parsing functions)
• I/O testing: simulate a client sending requests from a different process and check the responses are correct
• Internal state testing: simulate a client sending requests from a different process and check our intern

According to https://datatracker.ietf.org/doc/html/rfc2068#section-19.7.1, an HTTP/1.0 client is allowed to have a persistent connection using the Connection: keep-alive header. This means that we should verify/check this header also for HTTP/1.0 connections, and not only for 1.1.

Some instructions can easily be optimized such as:

const x = 5 + 5 can be optimized to const x = 10.
const myFunc = fn() { return 5 } can be optomized to return 5.