The Netherlands
I write code.
From Drew DeVault to ~sircmpwn/hare-dev
This allows you to write a global like so: let x: *int = &1234; It generates a second global on the fly to store the address operator's operand. Signed-off-by: Drew DeVault <sir@cmpwn.com> --- include/check.h | 2 + src/check.c | 2 +- src/eval.c | 171 +++++++++++++++++++++++++++-------------- tests/11-globals.ha | 4 + tests/26-regression.ha | 1 - [message trimmed]
From Drew DeVault to ~sircmpwn/sr.ht-discuss
We're doing our best to curb this behavior but it's an uphill battle. I'm sorry that your repo ended up being used for this.
From Drew DeVault to ~sircmpwn/sr.ht-dev
I think a ?depth parameter makes sense.
From Drew DeVault to ~sircmpwn/hare-dev
On Sat Mar 22, 2025 at 9:35 AM CET, Drew DeVault wrote: > net::http::response.body is not used in this design -- it's only useful > for the client. We can still keep one around in the response_writer but > it's an implementation detail, not part of the public API of the HTTP > server implementation. Clarification: I say we could keep an http::response around in the response_writer as an implementation detail, but I'm not sure it's necessary or helpful to.
From Drew DeVault to ~yerinalexey/public-inbox
Thanks!
From Drew DeVault to ~sircmpwn/hare-dev
On Fri Mar 21, 2025 at 5:00 PM CET, Willow Barraco wrote: >> let body: io::handle; >> let rw: http::response_writer; >> http::response_add_header(rw, "Content-Type", "text/html")!; >> http::response_copy(rw, body)!; >> >> OR: >> >> http::response_add_header(rw, "Content-Type", "text/html")!; >> http::response_add_header(rw, "Content-Length", "1234")!; >> io::copy(rw, body); >> >> WDYT? >
From Drew DeVault to ~sircmpwn/hare-dev
NACK, just created a sourcehut project instead.
From Drew DeVault to ~sircmpwn/hare-dev
Pushed after fixing a small syntax error. Thanks! To git@git.sr.ht:~sircmpwn/hare-http 9237448..2f018b0 master -> master
From Drew DeVault to ~sircmpwn/sr.ht-dev
We need to come up with a new design for the builds.sr.ht internal guest management and build distribution system. The goals are high-level and vaguely defined at this point, but it can probably be broken up into manageable chunks for a more concrete design proposal and implementation without doing it all at once. The high-level goals are as follows: == Refactoring how worker report to the build master == The workers currently have direct access to the database, albeit with a pg account with narrow permissions, but we would like to further constrain its sandbox by introducing worker-facing GraphQL resolvers for workers to use to perform the tasks they currently depend on the
From Drew DeVault to ~yerinalexey/public-inbox
Signed-off-by: Drew DeVault <drew@ddevault.org> --- Makefile | 99 +++++++++++++++++++-------------------- scripts/install-modules | 9 ++++ scripts/uninstall-modules | 8 ++++ 3 files changed, 66 insertions(+), 50 deletions(-) create mode 100755 scripts/install-modules create mode 100755 scripts/uninstall-modules diff --git a/Makefile b/Makefile index 28e96fb..b0d565f 100644 --- a/Makefile +++ b/Makefile @@ -10,23 +10,31 @@ SRCDIR = $(PREFIX)/src [message trimmed]