4 ms·
Can you expand on no 2? It seems an issue was opened 4 years ago, and was largely responded to with 'ok...soooo', and then closed when the opener apparently fo
by axaxs 6y ago
Can you expand on no 2? It seems an issue was opened 4 years ago, and was largely responded to with 'ok...soooo', and then closed when the opener apparently found a work around?
Not a cheap shot at the authors as you're right, other languages have or had this issue. But it still existing years later feels a bit ignored.
- steveklabnik 6y agoAs the person who closed it: when someone opens an issue, and then says "thanks I fixed my issue," the appropriate thing to do is for that ticket to be closed. Note that since then, other people have opened other issues, which haven't been closed, and we continue to talk about it. (Also, while I said in the thread and at the time "I am not aware of a flag or anything to turn this off, though I may be wrong.", at least today, that flag does exist.)
- axaxs 6y agoHey thanks for replying. Again, I didn't mean to point a finger at you or any of the team. Thanks for your work.
- rrss 6y agoOne person's (resolved) issue does not capture everything that happens with rust. https://github.com/rust-lang/rust/issues/41555 https://github.com/rust-lang/rust/issues/41555: "Tracking issue for Path Prefix Remapping", stabilized in 2018.