bug: anonymous nested tuples

[cristobal-montecino]

const std = @import("std");

fn print(args: anytype) void {
    std.debug.print("{}\n", .{args});
}
fn three(a0: u64, a1: u64, a2: u64) void {
    print(.{.{a0, a1, a2}});
}

pub fn main() !void {
    three(1,2,3);
}

Segmentation fault at address 0x202740
/home/ce/example.zig:7:15: 0x236f28 in three (output.s)
/home/ce/example.zig:11:10: 0x22fd0b in main (output.s)

Try this code

const std = @import("std");

fn print(args: anytype) void {
    std.debug.print("{}\n", .{args});
}
fn three(a0: u64, a1: u64, a2: u64) void {
    const args = .{a0, a1, a2};
    print(.{args});
}

pub fn main() !void {
    three(1,2,3);
}

struct:8:12{ .0 = struct:7:19{ .0 = 1, .1 = 2, .2 = 3 } }

Try this code

[edt-xx]

A data point. The following code fragment will seg fault. Changing the tuples with .{xxx} to .{"xxx"} and .{aaa} to .{"aaa"} works and the tuples are usable. Looks like it might be something that occurs when the nested tuples have runtime values.

fn gen() void {}
fn exactdiv() void {}
fn fanin() void {}
fn console() void {}

pub fn main() void {
    
var aaa:usize = 150;
var xxx:usize = 5;
    
const pipe =.{ 
    .{     gen, .{aaa} }, 
    .{"a", exactdiv, .{xxx} }, 
    .{"b", fanin}, 
    .{     console,   true}, 
    .{"a"},
    .{ exactdiv, .{7} }, 
    .{"b",              true} 
};

}

[andrewrk]

Fixed by deleting the stage1 codebase.