Disable wgpu-core documentation as a workaround for #4905.

[kpreid]

Connections
Proposed workaround for #4905.

Description
This enables cargo doc to succeed in a reasonable amount of time, as long as the reader isn't looking for documentation for wgpu-core itself.

Testing
Manually ran cargo doc and observed it succeeded, and checked the resulting wgpu-core and wgpu documentation.

Checklist

• Run cargo fmt.
• Run cargo clippy. If applicable, add:
  • --target wasm32-unknown-unknown
  • --target wasm32-unknown-emscripten
• Run cargo xtask test to run tests.
• Add change to CHANGELOG.md. See simple instructions inside file.

[cwfitzgerald]

Ah, nice workaround, we can also re-enable building docs in CI (currently also commented out)

[cwfitzgerald]

Would it be possible to add re-enabling CI to this PR?

[kpreid]

Would it be possible to add re-enabling CI to this PR?

Besides not building docs, there's a bunch of stale workaround stuff (just search for “4905” in comments), so I'd rather leave that to a separate PR in case of further messes.

[kpreid]

Oh, wait, I see — if we just enable the docs build now, then this PR gets that aspect tested. Okay.

[cwfitzgerald]

Amazing, thanks!

[kpreid]

Fixed changelog merge conflict.

Adjusting the CI script made me think: perhaps the “document wgpu-core anyway” should actually not be a feature but a bare cfg, so that --all-features doesn't enable it. But that means giving users who want the docs the pain of RUSTFLAGS.

[cwfitzgerald]

Hmmm, I think I like the cfg better as wanting this is going to be rare as it's so un-useful

[kpreid]

Hmmm, I think I like the cfg better as wanting this is going to be rare as it's so un-useful

Done.

[cwfitzgerald]

Noice