# Improving Test Runner API

**URL:** <https://ziggit.dev/t/improving-test-runner-api/5887>\
**Category:** Brainstorming\
**Tags:** language\
**Created:** [September 5, 2024, 6:08am UTC](https://ziggit.dev/t/improving-test-runner-api/5887 "2024-09-05T06:08:46Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![mnemnion](https://ziggit.dev/user_avatar/ziggit.dev/mnemnion/32/2478_2.png) [@mnemnion](https://ziggit.dev/u/mnemnion)\
**Post date:** [September 6, 2024, 1:55am UTC](https://ziggit.dev/t/improving-test-runner-api/5887/6 "2024-09-06T01:55:44Z")

</div>

> [@squeek502](#):
>
> Namespaces like `std.os.linux` and `std.os.windows` expect functions within them to only be referenced when targeting the relevant platform. An implicit `refAllDecls` would mean that these sorts of namespaces would cause compile errors, too.

This seems like another case of the [untouchable decls problem](https://ziggit.dev/t/a-not-immediately-fatal-way-of-indicating-that-a-feature-is-unavailable/4693) we had a thread about a while back.

Not as a obviously so, it says “refAllDecls”, and it does that. But blowing up with compile errors isn’t really the most useful semantics. Without some way to introspect a type at comptime and determine that referencing a decl will terminate compilation, it’s difficult to provide something more useful here.

---

_[View the full topic](https://ziggit.dev/t/improving-test-runner-api/5887)._