Add 'wgpu_device_destroy_render_pipeline()' function

[DavidPeicho]

Hi,

Nothing fancy, this PR simply forward the call wgpu_device_destroy_render_pipeline() to the render_pipeline_destroy() method in wgpu-core.

[kvark]

Thank you! Just one question

[DavidPeicho]

@kvark added a few more missing. I also renamed the added destroy functions to match what you previously did (I removed the "device" part of the name which isn't necessary). Let me know if you need anything else!

[kvark]

Thank you! Just one concern here

[kvark]

There is a bit of problem down the road - shared headers use destroy only on buffers and textures, and the semantics is different. We'll probably need to rename them to something else in wgpu-native.
But for now this is consistent with what we have.

[kvark]

Please squash and also run make so that the C header is updated.

[kvark]

Thank you!
bors r+

[bors]

Build failed:

• MacOS Nightly

[kvark]

Bah, nightly is all broken:

thread 'rustc' panicked at 'index out of bounds: the len is 0 but the index is 0', src/librustc_mir_build/hair/pattern/_match.rs:1184:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.45.0-nightly (9310e3bd4 2020-05-21) running on x86_64-apple-darwin

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 --crate-type lib

note: some of the compiler flags provided by cargo are hidden

error: could not compile `gfx-backend-metal`.

[kvark]

Filed as rust-lang/rust#72467

[kvark]

bors retry

[bors]

Build succeeded:

• Android Stable
• iOS Stable
• MacOS Nightly
• MacOS Stable
• MacOS Stable (Vulkan)
• Ubuntu Nightly
• Ubuntu Stable
• Windows Nightly
• Windows Stable