# Stabilization of items needed for no\_std applications?

**URL:** <https://internals.rust-lang.org/t/stabilization-of-items-needed-for-no-std-applications/5236>\
**Category:** Uncategorized\
**Created:** [May 12, 2017, 6:07pm UTC](https://internals.rust-lang.org/t/stabilization-of-items-needed-for-no-std-applications/5236 "2017-05-12T18:07:39Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![bascule](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/bascule/32/3057_2.png) [@bascule](https://internals.rust-lang.org/u/bascule)\
**Post date:** [July 18, 2017, 4:39am UTC](https://internals.rust-lang.org/t/stabilization-of-items-needed-for-no-std-applications/5236/8 "2017-07-18T04:39:41Z")

</div>

What would be really nice here are some default strategies for `#[panic_fmt]` which could be easily stabilized.

You could imagine something like:

`#[lang_default(panic_fmt, loop)]`

…which goes into an infinite loop. Or if you got the abort intrinsic working:

`#[lang_default(panic_fmt, abort)]`

One of the `no_std` environments I work in has a minimalist pseudo-libc that supports a few things like `printf()`, `abort()`, etc (although little else). Perhaps you could even have:

`#[lang_default(panic_fmt, print)]`

---

_[View the full topic](https://internals.rust-lang.org/t/stabilization-of-items-needed-for-no-std-applications/5236)._