port to meson cargoHEADmasterfeature/port-to-meson-cargo

Use the new unstable meson cargo support. This simplifies the
meson.build script and allows to use crates such as clap that require
picking up features from Cargo.toml.

This also allows us to not embed thiserror in subprojects, and instead
use a wrap file with a custom meson.build and some patches to make it
compile without running its build.rs script.

1 files changed, 0 insertions, 20 deletions

diff --git a/subprojects/thiserror/tests/ui/source-struct-unnamed-field-not-error.stderr b/subprojects/thiserror/tests/ui/source-struct-unnamed-field-not-error.stderr
deleted file mode 100644
index 1f5350b..0000000
--- a/subprojects/thiserror/tests/ui/source-struct-unnamed-field-not-error.stderr
+++ /dev/null
@@ -1,20 +0,0 @@
-error[E0599]: the method `as_dyn_error` exists for struct `NotError`, but its trait bounds were not satisfied
- --> tests/ui/source-struct-unnamed-field-not-error.rs:8:24
-  |
-4 | struct NotError;
-  | --------------- method `as_dyn_error` not found for this struct because it doesn't satisfy `NotError: AsDynError<'_>` or `NotError: std::error::Error`
-...
-8 | pub struct ErrorStruct(#[source] NotError);
-  |                        ^^^^^^^^^ method cannot be called on `NotError` due to unsatisfied trait bounds
-  |
-  = note: the following trait bounds were not satisfied:
-          `NotError: std::error::Error`
-          which is required by `NotError: AsDynError<'_>`
-note: the trait `std::error::Error` must be implemented
- --> $RUST/core/src/error.rs
-  |
-  | pub trait Error: Debug + Display {
-  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-  = help: items from traits can only be used if the trait is implemented and in scope
-  = note: the following trait defines an item `as_dyn_error`, perhaps you need to implement it:
-          candidate #1: `AsDynError`