Meghan Denny
Meghan Denny
should this be a compile error since bit count is undefined for `comptime_int` ?
~~yes. btw i'm only referring to the first argument so you'd have to do something like `@shlExact(@as(u32, 1), 1)` ?~~
personally i would assume the error message to be that you're missing `const` or `var` on baz
``` thread 875350 panic: reached unreachable code /home/meghan/src/zig/src/codegen/llvm.zig:8327:56: 0x15f108f in airMemset (zig) const len = self.sliceOrArrayLenInBytes(dest_slice, ptr_ty); ^ /home/meghan/src/zig/src/codegen/llvm.zig:4466:54: 0x1107b1a in genBody (zig) .memset_safe => try self.airMemset(inst, true), ^ /home/meghan/src/zig/src/codegen/llvm.zig:1215:19:...
behavior changed in master, tests are not currently expected to output https://github.com/ziglang/zig/issues/15091 also related https://github.com/ziglang/zig/issues/5738 edit there was another related issue but i cant find it atm
`test` blocks are meant to be whats commonly referred to as "unit tests" and should generally not have observable side effects
while developing you can also put it in a `pub fn main() !void {}` and move to `test {}` once it is ready
title should like be "doesn't"
`orelse` isnt eager in its evaluation atm even for consts. that's why `a orelse unreachable` and `a.?` have different behavior for comptime-known optionals.
maybe related #14706