Is this the right way to construct Io.Evented?
var ev: std.Io.Evented = undefined;
try ev.init(
alloc,
std.Io.Evented.InitOptions{
.backing_allocator_needs_mutex = false,
},
);
Using zig 0.16.0-dev.2962+08416b44f.
Is this the right way to construct Io.Evented?
var ev: std.Io.Evented = undefined;
try ev.init(
alloc,
std.Io.Evented.InitOptions{
.backing_allocator_needs_mutex = false,
},
);
Using zig 0.16.0-dev.2962+08416b44f.
For a bit more context, I’m working on a minimal segfault repro related to Io.Evented here: https://codeberg.org/jackdev/mdt/src/branch/segfault_repro/scripts/segfault_repro.sh. But I’m still in the stage of trying to narrow down whether it’s an issue with my usage.
I’m suspicious of the way I allocate futures on the heap as well for potentially being wrong: https://codeberg.org/jackdev/mdt/src/commit/1fd89ca8e94d13f89b2dbb75a7f1e97e027f6d6d/src/href_extractor.zig#L10-L17.