From Noam Preil to ~sircmpwn/hare-dev
Signed-off-by: Noam Preil <noam@pixelhero.dev> --- content/tutorials/introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tutorials/introduction.md b/content/tutorials/introduction.md index dd22c3a..e3120cb 100644 --- a/content/tutorials/introduction.md +++ b/content/tutorials/introduction.md @@ -1303,7 +1303,7 @@ sections: is shown here as well: pointer arithmetic and conversions between pointer types. Using casts, you can instruct Hare to treat some memory as if it were a given type, regardless of if it actually is or not. Use with cation. [message trimmed]
From Noam Preil to ~sircmpwn/hare-dev
Signed-off-by: Noam Preil <noam@pixelhero.dev> --- cmd/hare/subcmds.ha | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cmd/hare/subcmds.ha b/cmd/hare/subcmds.ha index 60ad3d5..ac0bc15 100644 --- a/cmd/hare/subcmds.ha +++ b/cmd/hare/subcmds.ha @@ -179,6 +179,9 @@ fn build(args: []str) void = { case !exec::exit_status => fmt::fatal("{} {}: build failed", os::args[0], os::args[1]); }; if (tty::isatty(os::stdout_file)) { [message trimmed]
From Noam Preil to ~sircmpwn/hare-dev
Signed-off-by: Noam Preil <noam@pixelhero.dev> --- content/blog/2021-10-05-Reflection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2021-10-05-Reflection.md b/content/blog/2021-10-05-Reflection.md index cd1efc0..9ab1d28 100644 --- a/content/blog/2021-10-05-Reflection.md +++ b/content/blog/2021-10-05-Reflection.md @@ -9,7 +9,7 @@ I've just merged support for reflection to Hare. Here's how it works! ## Background "Reflection" refers to the ability for a program to examine the type system of its programming langauge, and to dynamically manipulate types and their values [message trimmed]
From Noam Preil to ~sircmpwn/aerc
--- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 323de86..5338dbf 100644 --- a/README.md +++ b/README.md @@ -4,8 +4,8 @@ aerc is an email client for your terminal. A short demonstration can be found on [https://aerc-mail.org/](https://aerc-mail.org/) Join the IRC channel: [#aerc on irc.freenode.net](http://webchat.freenode.net/?channels=aerc&uio=d4) for end-user support, and [#aerc-dev](http://webchat.freenode.net/?channels=aerc-dev&uio=d4) [message trimmed]
From Noam Preil to ~andrewrk/ziglang
Hi, My two cents: I think adding a native type, and removing the stdlib type, makes sense. I disagree that LLVM not having native support is a compelling reason to avoid it. LLVM also lacks support for a lot of other features Zig provides, which makes sense, because LLVM is a *low-level IR*. Additionally, major decisions about the language (whether a type should be builtin qualifies, IMO) should not be made based on the limitations of the stage1 compiler, or the decisions of an external project. That said, having translate-c produce code using std.math.Complex would also be an acceptable solution. However, it would be the first case of C code that cannot automagically be translated to raw Zig code. This would
From Noam Preil to ~sircmpwn/public-inbox
Hi, Just wanted to note that there's a difference between zig the language and Zig the LLVM-based compiler, and give my two cents. I'm currently working on a compiler[1] that supports both Zig and BTR as input languages (though the BTR frontend has not yet been written, as I'm finishing up ARM64 codegen first), is written in pure C99 (and is primarily tested on plan9!), and with a focus on compiler simplicity and correctness. Zig the language is more complex than BTR, but is arguably simpler than C in many respects. Zig the compiler (both the LLVM-based stage1 and the self-hosted compiler) are absolutely more complex than BTR, and small C compilers like cproc or kencc, but that is an implementation concern; the language allows for simpler
From Noam Preil to ~pixelherodev/cyclopropatriene-devel
+ new_path = file_rel_dir(ctx.path, ctx.token.ptr, ctx.token.len); + new_path_len = strlen(new_path); Maybe make file_rel_dir take a pointer to len and store it if nonnull, to avoid recalculating an already known length. +file_rel_dir(const char *const orig, const char *const new, size_t new_len) + out = malloc(last_slash_pos + strlen(new)); strlen(new) is illegal here, since new is not required to be null terminated. Furthermore, we have the length as new_len.
From Noam Preil to ~pixelherodev/cyclopropatriene-devel
Note to self for tomorrow when i review this properly: children list in single processed queue is flat heaped list and should be freed as such.
From Noam Preil to ~sircmpwn/public-inbox
I think it is intended to make indexing easier for Google.
From Noam Preil to ~sircmpwn/chartsrv-devel
--- main.go | 131 ++++++++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 108 insertions(+), 23 deletions(-) diff --git a/main.go b/main.go index de770d6..c8af46b 100644 --- a/main.go +++ b/main.go @@ -142,7 +142,7 @@ func metricName(metric map[string]string) string { return out + "{" + strings.Join(inner, ",") + "}" } func handleLabel(p *plot.Plot, l *plotter.Line, label string, tags map[string]string) { func handleLabel(p *plot.Plot, l plot.Thumbnailer, label string, tags map[string]string) { [message trimmed]