Dealing with strings

[chung-leong]

One of the more problematic part of Zigar is the inability to convert arrays of bytes into a string on the JavaScript side. Most of the times []const u8 represents a string but we can't really make that assumption. It's entirely possible for the pointer to point to bytes that don't form a text string.

[chung-leong]

The current idea is to look up a struct type named @"meta(zigar)" in the root Zig file. It's expected to contain certain functions that allow you to control how fields are exported. One of them is going to be isString()`:

pub const @"meta(zigar)" = struct {
    pub fn isString(comptime T: type, comptime field_name) bool {
        // ...
    }
};

In the first version where the feature is introduced, []const u8 and []const u16 will be treated as slices of numbers unless specified otherwise. After that the default assumption will be that they're strings.