Re:Don't setenv in multi-threaded code on glibc
by gens on Tuesday January 31, 2017 @11:35AM
(#13532100)
From one (or more) of the comments here you can see that the reasoning for rust in topics about C is "everybody should write rust instead of C". At least for some people.
One other comment got it right, it is annoying to have multiple rust comments in every thread about C.
But you are right, best way to deal with these kinds of... i don't want to be rude, is ignoring.
PS Thank you for addressing the rest of the comment, not just the part you made personal.
Why do you get to decide? There are a lot of people in this thread talking about similar issues in other languages (Python, Rust, etc) and other functions (like fopen() and exit()). I think those discussions are very on-topic.
Why isn't this topic about "issues between threads and setenv in any language that uses glibc"?
Why isn't this topic about "issues between threads and other functions in any language that uses glibc"?
If you don't like a particular conversation in this topic, you can collapse it and move on.