François Mockers

Then is it really a good idea to have things on docs.rs that users won't find when they try to use them? I think docs.rs can't yet automatically mark those...

serde is still enabled in the default features. the serialise feature wasn't done in all sub crates, and bevy_gltf has a mandatory dependency on serde anyway

done in https://github.com/bevyengine/bevy/pull/12366

@ItsDoot merging this PR fails because of missing implementations of `drain` and `pop` which were added in #5728 and #5797. Could you add those? thanks!

Choosing between `rustls` or `native-tls` is done by feature: https://github.com/mockersf/serde_dynamodb/blob/de4da2b8d27163881804d7755635c992e2a0a3f7/Cargo.toml#L25-L29 This can happen if you have both feature `rustls` and `native-tls` enabled at the same time, or if you have...

you could imagine going through every call in an example to the asset server and looking at the files loaded, but I think that's way too complex for what it's...

we are moving more and more to clippy configuration, and lint management on crate level, so I'm not sure this part is relevant anymore

does it segfault also with `--release`?

> This does not guarantee all of these crates will build for `no_std` environments. Many still have dependencies with `std` deps. Are at least a few of the crates `no_std`...

Yup, this is the goal behind https://github.com/bevyengine/bevy/pull/5550