NY
Software Engineer | Go | Rust | Hare | Linux | MS in CS candiate at omscs.gatech.edu | RebelGeek | Strongly typed native Masshole
From Blain Smith to ~sircmpwn/hare-dev
I've been working on a BPF module with my own versions of these structs and definitions, but I figured it was worth issuing a patch to get them included in the Linux runtime here. I kept the names of the struct fields as close as possible to the kernel versions. Signed-off-by: Blain Smith <rebelgeek@blainsmith.com> --- rt/+linux/socket.ha | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/rt/+linux/socket.ha b/rt/+linux/socket.ha index 988e1514..b9019ee4 100644 --- a/rt/+linux/socket.ha +++ b/rt/+linux/socket.ha [message trimmed]
From Blain Smith to ~sircmpwn/hare-dev
That is fine with me. I am happy to take a pass at actually filling out the README files with something and sending another patch.
From Blain Smith to ~sircmpwn/hare-dev
Modules such as net::ip, net::tcp, and net::udp do not appear on https://docs.harelang.org/net so this merely adds empty README files to modules that have it missing so HTML docs get generated for them. Rather than filling in documentation for each module I opted to place empty files to get them to at least show up and let module maintainers fill them in as they see fit. Fixes: https://todo.sr.ht/~sircmpwn/hare/911 Signed-off-by: Blain Smith <rebelgeek@blainsmith.com> --- crypto/sha1/README | 0 crypto/sha256/README | 0 hare/unit/README | 0
From Blain Smith to ~sircmpwn/hare-users
Yes, you can. A few examples are: - https://git.sr.ht/~blainsmith/hare-sqlite - https://git.sr.ht/~sircmpwn/hare-sdl2
From Blain Smith to ~blainsmith/public-inbox
Thanks!
From Blain Smith to ~blainsmith/public-inbox
Thanks!
From Blain Smith to ~sircmpwn/hare-dev
Apologies, I will get that taken care of.
From Blain Smith to ~sircmpwn/hare-dev
Apologies, I will get that taken care of. On Mon, Oct 30, 2023 at 5:16 AM Drew DeVault <sir@cmpwn.com> wrote: > > Does not apply, rebase?
From Blain Smith to ~sircmpwn/hare-dev
This extends read_statusline to support both request and response types. This will be needed when there is a server implementation to read incoming requests. One thing that is rather awkward is setting the request.target with empty values since uri::parse() fails to parse scheme, host, and port-less URIs. Signed-off-by: Blain Smith <rebelgeek@blainsmith.com> --- net/http/client.ha | 1 + net/http/do.ha | 136 +++++++++++++++++++++++++++++++++--------- net/http/request.ha | 3 + net/http/transport.ha | 6 +- 4 files changed, 116 insertions(+), 30 deletions(-) [message trimmed]
From Blain Smith to ~sircmpwn/hare-dev
Signed-off-by: Blain Smith <rebelgeek@blainsmith.com> --- net/http/client.ha | 2 ++ net/http/do.ha | 4 ++-- net/http/transport.ha | 4 ++-- 3 files changed, 6 insertions(+), 4 deletions(-) diff --git a/net/http/client.ha b/net/http/client.ha index fed803e..1e2edbd 100644 --- a/net/http/client.ha +++ b/net/http/client.ha @@ -57,6 +57,8 @@ fn new_request(client: *client, method: str, target: *uri::uri) request = { req.target.port = 80; case "https" => [message trimmed]