Hey all,

I'm getting close to having tests passing in the copy elision project.

Once the Zig test suite all passes, I'd like to merge the branch. It's
already diverged uncomfortably far from master, so I really want to wrap
it up.

However, it's likely to introduce a lot of new bugs. This branch
represents a huge amount of code churn, in the most complicated part of
the compiler. Various assumptions that previously held, no longer hold,
and that inevitably causes bugs. We have lots of tests, but nowhere near
full coverage.

So! If you have an active, open source Zig project which has an obvious
way to build and/or run tests, share a link with me here. I'm not going
to make any promises, but this will give me the opportunity to test your
code and extract additional test cases before merging the copy-elision
branch.

Cheers,
Andrew

Hi Andrew

Here are a few projects which may be helpful.


```
git clone https://github.com/tiehuis/zig-regex
cd zig-regex && zig build
```

Requires libpcre. C results should match Zig results. This would be
actually be useful to see if there are any notable performance gains
on the new branch vs. the current.

```
git clone https://github.com/tiehuis/zig-benchmarks-game
cd zig-benchmark-games && ./run
```

```
git clone https://github.com/tiehuis/zig-ryu
cd zig-ryu && ./build.sh && ./bench-zig
```

Marc


On Tue, Jan 8, 2019 at 8:38 AM Andrew Kelley <andrew@ziglang.org> wrote:
>
> Hey all,
>
> I'm getting close to having tests passing in the copy elision project.
>
> Once the Zig test suite all passes, I'd like to merge the branch. It's
> already diverged uncomfortably far from master, so I really want to wrap
> it up.
>
> However, it's likely to introduce a lot of new bugs. This branch
> represents a huge amount of code churn, in the most complicated part of
> the compiler. Various assumptions that previously held, no longer hold,
> and that inevitably causes bugs. We have lots of tests, but nowhere near
> full coverage.
>
> So! If you have an active, open source Zig project which has an obvious
> way to build and/or run tests, share a link with me here. I'm not going
> to make any promises, but this will give me the opportunity to test your
> code and extract additional test cases before merging the copy-elision
> branch.
>
> Cheers,
> Andrew
>