# Setting cfg(nightly) on nightly by default

**URL:** <https://internals.rust-lang.org/t/setting-cfg-nightly-on-nightly-by-default/1893>\
**Category:** Uncategorized\
**Created:** [April 15, 2015, 10:52pm UTC](https://internals.rust-lang.org/t/setting-cfg-nightly-on-nightly-by-default/1893 "2015-04-15T22:52:55Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![DanielKeep](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/danielkeep/32/1332_2.png) [@DanielKeep](https://internals.rust-lang.org/u/DanielKeep)\
**Post date:** [January 20, 2017, 4:30am UTC](https://internals.rust-lang.org/t/setting-cfg-nightly-on-nightly-by-default/1893/24 "2017-01-20T04:30:03Z")

</div>

I’d like a nicer, more convenient syntax for it, too.

That’s _partly_ why I’m arguing _against_ it, here. Having to use `build.rs` _is_ clunky, but maybe imposing a bit of separation and inconvenience isn’t a bad thing. I’ve seen some _really_ horrific codebases using conditional compilation.

Plus, every time I try to imagine how to introduce named custom `cfg`s directly in Rust source, it starts to smell of Inner Platform Effect, at which point I go think about something else.

---

_[View the full topic](https://internals.rust-lang.org/t/setting-cfg-nightly-on-nightly-by-default/1893)._
