Got a lot of comptime related errors after update to zig 0.11

[CGQAQ]

Zig Version

0.11

Steps to Reproduce and Observed Behavior

compile bun with 0.11.0 or 0.12.0

compiler errors emitted:
0.11.0
0.12.0-dev.157+8e96be008

I think it's related to https://ziglang.org/download/0.11.0/release-notes.html#Forbid-Runtime-Operations-in-comptime-Blocks-

see oven-sh/bun#4233 (comment) for context

An example in these errors:

src/bun.js/api/bun/dns_resolver.zig:1144:31: note: struct requires comptime because of this field
    pending_host_cache_cares: PendingCache = PendingCache.init(),

pub const DNSResolver = struct {
    pending_host_cache_cares: PendingCache = PendingCache.init(),
    //  ^ I don't think this will force DNSResolver to be comptime
};
const PendingCache = bun.HiveArray(GetAddrInfoRequest.PendingCacheKey, 32);
pub fn HiveArray(comptime T: type, comptime capacity: u16) type {
      return struct {
           const Self = @This();
           buffer: [capacity]T = undefined,
           available: std.bit_set.IntegerBitSet(capacity) = std.bit_set.IntegerBitSet(capacity).initFull(),
           pub const size = capacity;

           pub fn init() Self {
               return .{};
           }
     };
}

Expected Behavior

Maybe should've not got these errors? not very sure.

[CGQAQ]

caused by

pub const WriterType: type = @typeof(WriteStream(Source.StreamType, undefined));

I accidentally @TypeOfed a type, but the compiler errors is not correct at all IMO

See:
oven-sh/bun#4233 (comment)

[rohlem]

the compiler errors is not correct at all IMO

Not sure I agree (@TypeOf(type) is perfectly legal), but at least transitively pointing to the member(s), and noting that its type is type, would be helpful.