Do we allow cycles in modules?

[k2d222]

// module matrix.wesl

fn rotation(angle: f32) -> mat2x2f {
    return mat2x2f(
        cos(angle, -sin(angle),
        sin(angle), cos(angle)
    );
}

fn sum_components(m: mat2x2f) -> f32 {
    return vector::sum_components(m[0]) + vector::sum_components(m[1]);
}

// module vector.wesl

fn rotate(v: vec2f, angle: f32) -> vec2f {
    return matrix::rotation(angle) * v;
}

fn sum_components(v: vec2f) -> f32 {
    return v[0] + v[1];
}

vector::rotate depends on matrix::rotation and matrix::sum_components depends on vector::sum_components. Some languages allow that (rust, javascript) while others don't (c++, python in some cases, java IIRC). What should we do in WESL?

[stefnotch]

My vote is to allow cycles.

However, there is at least one case that is still illegal.

// foo.wesl
import bar::b;
const a = b + 1;

// bar.wesl
import foo::a;
const b = a + 1;

(a depends on b which depends on a)
Basic linker implementations don't need to check for this though. Generating broken code and letting naga/tint complain is fine.