Nemo157

We'd also need to have TLS in the container if it is exposed to the internet, but I assume we're still having it only accessed by cloudfront over a private...

Hmm, is crates.io bundling the sdk into their js? I did load it to check and didn't see any connection to the sentry cdn.

Ah yes, inspecting the bundle I do see it embedded. We could do the same which would at least mean that there's no connection to load the sdk. There'd still...

Ah, and that usage of sentry is mentioned explicitly in the crates.io section of the privacy policy, so I think we definitely should be adding it to the docs.rs section...

Given the RFC proposes edition-gating the warning, as long as `SUC` (or whatever other API is proposed) is stabilized by the first release of the 2024 edition there should be...

I was thinking about the coherence issue again today, the one presented in boats blog post was that this introduces a diamond incoherence: ``` impl IntoIterator for T { }...

> only implementing `Unpin` for generators that don't borrow across `yield`s, like what `async` already does with `await` `async` does not do that, async-fn and async-blocks both create generated future...

It should be possible to ship images as a separate optional dependency with this RFC, assuming rustdoc tracks spans for relative path references ```toml # bevy/Cargo.toml [features] example-images = ["dep:bevy-example-images"]...

It sounds like the missing step there is the ability to mark your crate as unsafe ```rust /// SAFETY: We require users of this crate to promise there is no...

> We have the same issue with unsafe attributes: do they mean that the API consumers must uphold extra invariants, _or_ that the function author promises that some invariants are...