Kyle J Strand

@decathorpe Do you know how `nalgebra`'s cargo-publish CI is set up? I would be surprised if it's run on Windows for some reason. (Also, I'm kind of surprised to hear...

...possibly related, and probably a bug (though apparently a `cargo` one rather than a `bundle-licenses` one): it looks like, if the license file is a symlink, the generated "license text"...

As an alternative to changing the behavior of the existing `format`, how about a separate extension-trait on copyable _sources_ of iterators providing a "safe format" type, so that `into_iter()` is...

> ..., our job is to provide consistent and predictable semantics to our users whenever that is possible with reasonable performance. It's difficult for me to object to this, because...

It's also important to note that having a more "sane" behavior for unwinding is the _entire point_ of `extern "C-unwind"`. It exists specifically because of the problems inherent in making...

> Why should I not be afforded the luxury of a sane semantics in that case? Because, in that case, "abort" *is* the "sane semantics" you are afforded. Providing further...

@rustbot ready

@rust-lang/libs I think we need some official sign-off of some sort on this, because it provides a new guarantee that wasn't part of the initial RFC. If there's agreement that...

@chorman0773 > If someone, for example, called into MinGW code using SJLJ exceptions from MinGW compiled to use SEH, it wouldn't be able to interact with the exception at all...

The [`llvm.loop` metadata interface](https://llvm.org/docs/LangRef.html#llvm-loop) itself actually seems like a pretty well-named set of traits. In particular, I like the idea of the names having a sort of namespacing using `.`,...