Žiga Željko

@svaarala I'm pretty sure the approach by @seanmiddleditch can be adapted to the current expression parser. The parser emits code as usual while also keeping track of: * the end...

If your photos are already in JPEG format, I doubt that FLIF would compress them any better. You should probably check out Lepton (https://github.com/dropbox/lepton), which is made specifically for such...

@Sizik How would element access work in this case? Would you be able to use `.x`, `.y`, `.z`, `.w`?

> Perhaps some way to assign names to array slots would be nice. This could be solved with something like #793: ```zig const Axis = enum { x, y, z...

Targeting plan9 might be a bit trickier, since it uses a custom binary format which LLVM does not currently support (see http://man.cat-v.org/plan_9/6/a.out). From what I read, outputting that format should...

> is that not the same `a.out` kinda file No. The `a.out` file that gets output by default is actually in ELF (or MachO) format, and has no relation to...

@g-w1 By the way, is the plan9 syscall ABI (i.e. the stuff in `os/plan9/x86_64.zig`) documented anywhere?

The page you linked describes the API provided by libc. What I'm looking for is the underlying ABI (application **binary** interface) provided by the kernel -- how the values are...

> There wouldn't be a clear difference between `anytype` and `infer`, though. The only difference is that with `infer`, the type has a name, while with `anytype`, it doesn't. There...

There is a simpler and more powerful way that does not depend on memoization or other type constructor shenanigans. Given a parameter declaration such as `haystack: ArrayList(infer T)`, the compiler...