News for hackers. Stuff that matters.
Re:Baby Steps: Slowly Porting Musl to Rust by dikaiosune on Sunday June 12, 2016 @01:56PM (#11889316)
Panics are possible with #![no_std], but it does require that you supply a working implementation of panic_fmt, which I haven't gotten to yet (mostly because I was waiting on panic-as-abort to land which it recently did).
Re:Baby Steps: Slowly Porting Musl to Rust by CUViper on Sunday June 12, 2016 @02:40PM (#11889576)
OK, another option is to make it an explicit infinite "loop{...}" which only exits by returning. The "0.." is effectively infinite anyway, because it will overflow freely in release mode. (But surely you'll hit an invalid memory page before that happens.)
Re:Baby Steps: Slowly Porting Musl to Rust by dikaiosune on Sunday June 12, 2016 @02:44PM (#11889592)
You're right, I think this version is a bit clearer:

https://is.gd/lck8c7

Re:Baby Steps: Slowly Porting Musl to Rust by steveklabnik on Sunday June 12, 2016 @02:02PM (#11889342)
NB: you still need panic_fmt with panic == abort; the default panic handler still prints a message, even though it doesn't go through with the unwinding.
Re:Baby Steps: Slowly Porting Musl to Rust by loeg on Sunday June 12, 2016 @05:24PM (#11890325)
panic_fmt can be as simple as (C pseudocode):

    printf("...");
    kill(getpid(), SIGABRT);
    while(true)
      /* In case kill(ABRT) returns, halt. */;