# build runner: don't incorrectly omit reference traces · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/46d7e808dcef3c9f9200d6cc1ed4e3a787ba054d)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 46d7e808dcef3c9f9200d6cc1ed4e3a787ba054d

Requested commit: 46d7e808dcef3c9f9200d6cc1ed4e3a787ba054d

Commit: 46d7e808dcef3c9f9200d6cc1ed4e3a787ba054d

Tree: c89e8bde28f46f77d1b3863a841fc2535cb1788a

Author: mlugg

Committer: mlugg

## Message

```
build runner: don't incorrectly omit reference traces

It's incorrect to ever set `include_reference_trace` here, because the
compiler has already given or not given reference traces depending on
the `-freference-trace` option propagated to the compiler process by
`std.Build.Step.Compile`.

Perhaps in future we could make the compiler always return the reference
trace when communicating over the compiler protocol; that'd be more
versatile than the current behavior, because the build runner could, for
instance, show a reference trace on-demand without having to even invoke
the compiler. That seems really useful, since the reference trace is
*often* unnecessary noise, but *sometimes* essential. However, we don't
live in that world right now, so passing the option here doesn't make
sense.

Resolves: #23415

```

## Parents

- [16481c8ef347f7fc5ffdc4636cf904b335a6dc09](https://git.cafe/gitcafe/zig/commit/16481c8ef347f7fc5ffdc4636cf904b335a6dc09?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/46d7e808dcef3c9f9200d6cc1ed4e3a787ba054d?format=markdown)