@Type(@typeInfo(c_int)) != c_int

[DerryAlex]

Zig Version

0.11.0-dev.1580+a5b34a61a

Steps to Reproduce and Observed Behavior

const std = @import("std");

pub fn main() void {
    const Cint = @Type(@typeInfo(c_int));
    std.log.info("{} {} {}", .{ c_int == i32, Cint == c_int, Cint == i32 });
}

on linux amd64:

info: false false true

Expected Behavior

Not sure if this is intended. It is quite confusing.

1. If this is intended, it should be documented.
2. Or c_int and i32 has different internal type id, but c_int == i32 holds on amd64 targets and c_int == i16 holds on some embedded targets.

[InKryption]

This is also the case for usize/isize, last I checked.

[Arya-Elfren]

Am I understanding it correctly that this is basically saying:

If you have a non-zig type (c_*) and you want its platform specific zig-native equivalent you just create a new type with @Type from its @typeInfo

Because @Type will prefer the zig versions of the types and there is no "type info provenance" that would tell it that this is supposed to be a c type?

edit:
Not even just c types but platform varying types in general, like usize/isize.

[EtienneParmentier]

I believe platform dependant types should be aliases instead of different types entirely, it would make reasoning about them much more intuitive. Is there any problem with this approach ?