structio-derive 0.4.0

The optional #[derive(Structio)] for structio. Enable structio's `derive` feature rather than depending on this crate directly.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

//! Each misuse of an attribute, refused at the attribute.
//!
//! The expected output next to each case is the derive's own message, spanned
//! where the user wrote the thing it refuses. These are stable across
//! compiler versions because none of them reaches the macros or the type
//! checker: the derive refuses before it expands. That placement is the thing
//! being tested, so the comparison stays `nocompile`'s default `Exact`, which
//! keeps the span art a `Brief` run would drop.
//!
//! Skipped on Windows, where `nocompile` declines to claim support: it folds
//! separators and strips `\r` under unit test, but its author has no Windows
//! machine to confirm that on. Untested rather than known broken, so the test
//! is `ignore`d there rather than compiled out -- `cargo test -- --ignored` on
//! a Windows box is what would settle it. The other two CI platforms run the
//! suite, and nothing about a rejected attribute is host-specific.

#[test]
#[cfg_attr(windows, ignore = "nocompile does not claim Windows support in v1")]
fn misuse_is_refused_at_the_attribute() {
    let mut t = nocompile::cases!();
    t.dependency_path("structio", "..");
    // The fixtures write `structio::Structio`, the re-export behind structio's
    // `derive` feature. The generated project depends on structio by path, so
    // the feature goes on the only way a manifest can turn on a dependency's
    // feature from outside: a default feature that forwards to it.
    t.raw_manifest_lines("[features]\ndefault = [\"structio/derive\"]");
    t.compile_fail_dir("tests/ui");
    t.assert();
}