"disclaimer: I'm the founder of Plandex: an open source AI coding agent"

Note that I wouldn't personally add "open source", I don't think it adds to the discussion, but it's what I would have expected to see.

I mean, I discuss AI a lot on HN. Do I need to include a disclaimer on every comment?

But the open source project is free, full-featured, MIT licensed, and will stay that way.

It also has paying customers via cloud-hosting options, and the economics are working out well so far, fwiw. Lots of work to do, but it's on track to be both a sustainable open source project and a sustainable business.

I'm sorry if that still doesn't meet your lofty moral standards—all I can really say is I'm trying my best to get the balance right.

  warning: expression in static assertion is not an integer constant expression [-Wpedantic]

  #define C(x) ( (void)sizeof( (char [(int)(x) || 1]){0} ), (x) )

since the underlying storage is std::array<char, ...>, it's alignment may be less that the required alignment of the requested type and that of the pointers being stored in the free list.

  #include <cstdio>
  
  namespace detail {
  template<size_t N>
  struct Capitalize {
    char data[N];
    constexpr Capitalize(const char (&tag)[N]) : data{} {
      for (size_t i = 0; i < N; i++)
        data[i] = tag[i];
      data[0] &= 95;
    }
  };
  }
  
  template<typename T, size_t N, const char (&tag)[N], size_t count>
  struct MyType {
    static constexpr auto capitalized = detail::Capitalize(tag);
    constexpr auto name() const {
      return capitalized.data;
    }
    T array[count];
  };
  
  int main() {
    static constexpr char hello[] = "hello";
    MyType<int, sizeof(hello), hello, 10> value{};
    std::puts(value.name());
  }

Furthermore, why is type traits among the list of features that you claim is subsumed by comptime? not only is that not the case, but type traits are not so much a feature of C++ as they are of its standard library, implemented using templates (a feature of the language).

  error: type capture contains reference to comptime var

  fn capitalize(tag: []u8) []u8 {
      tag[0] &= 95;
      return tag;
  }

  fn MyType(T: type, comptime tag: []u8, comptime count: usize) type {
      const capitalized = capitalize(tag);
      return struct {
          fn name() []const u8 {
              return capitalized;
          }
          array: [count]T,
      };
  }

  pub fn main() void {
      comptime var hello: [5]u8 = undefined;
      @memcpy(&hello, "hello");

      var v: MyType(i32, &hello, 10) = undefined;
      v.name();
  }

Then again, it doesn't hurt to be pedantic.

  usage: weeks YYYY-MM-DD YYYY-MM-DD
  
  weeks () {
      one_day=$((60 * 60 * 24))
      unix_from=$(date +%s --date="$1")
      unix_to=$(date +%s --date="$2")
  
      while [ $unix_from -lt $unix_to ]
      do
          echo @$unix_from
          unix_from=$((unix_from + one_day))
      done | date +'%F w%V %a' -f -
  
      unset -v one_day unix_from unix_to
  }

Static binaries generated by Go are indeed large, even if the source code here is under 30 lines with support to some additional minor features (US and Finnish day names, command line help, optional week headings, day counts and parameter handling).

Here are some more scripts to generate calendar.txt date format:

https://terokarvinen.com/2024/format-date-calendar-txt/

This issue is sidestepped in TFA by using a union, which ensures appropiate alignment for all it's members, but in the library there's nothing which prevents me from asking for a chunk size of, say, 9 bytes, which would store pointers at misaligned addresses when creating the free-list.

    package main

    import "fmt"

    func main() {
        fmt.Println("Hello world")
    }

https://gist.github.com/erinok/4399bbb1ea535deac051781eb9177...