Re: rustc panic

[Swift Griggs <swiftgriggs%gmail.com@localhost>]

On Wed, 26 Jul 2017, Joerg Sonnenberger wrote:
> I have no idea what rust is doing here or why it thinks it should be 
> doing something.

Am I reading this wrong or does it appear that libpthread is somehow 
entangled with the Rust language interpreter ? Maybe that's intentional 
and I'm just ignorant, but that seems, uhh, weird/wrong. Why would someone 
do such a thing?

> At this point I can only conclude that rust is broken and continue 
> fixing real bugs.

<rant>
I may be off-topic here, but I have to say this type of thing is getting 
annoying for me too because I'm often porting C-language code to old/weird 
platforms besides NetBSD, and more and more I run into issues where 
someone gets hyperexcited over some newish language like Rust, Go, D, 
etc... and then somehow think the rest of the world wants their C code 
polluted with that crap^H^H^H^H uhm, I'm mean stuff. Also, I'm not sure 
why people go back and change ANSI-isms and C99-isms into C11-isms. Did 
someone ban C99 ? Is it breaking anything ?

You will pry C from my cold dead hands, kids. Sorry, but I'm not moving to 
cool-language-X, so it'd be nice if they didn't come in and break my world 
every so often in the name of "progress". Though, usually in NetBSD it's 
just a simple mistake or misunderstanding, rather than any aforementioned 
acute lack of clue.
</rant>

So, from my admittedly very limited perspective, I'm right there with you 
on the "rock on and carry on" maneuver Joerg, as you so appropriately 
advocate. "Fixing real things" as you put it gets you a high five from the 
plebs down here in userland, especially me. Unbreaking Rust issues? 
uhhhhh... not so much.

-Swift