File: spike-neg2.rs

package info (click to toggle)
rustc 1.88.0%2Bdfsg1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 934,128 kB
  • sloc: xml: 158,127; python: 36,062; javascript: 19,855; sh: 19,700; cpp: 18,947; ansic: 12,993; asm: 4,792; makefile: 690; lisp: 29; perl: 29; ruby: 19; sql: 11
file content (53 lines) | stat: -rw-r--r-- 1,182 bytes parent folder | download | duplicates (15)
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
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
// A variant of the first "spike" test that serves to test the
// `rustc_partition_reused` and `rustc_partition_codegened` tests.
// Here we change and say that the `y` module will be codegened (when
// in fact it will not), and then indicate that the test itself
//@ should-fail (because an error will be reported, and hence the
// revision rpass2 will not compile, despite being named rpass).

//@ revisions:rpass1 rpass2
//@ should-fail
//@ compile-flags: -Z query-dep-graph

#![feature(rustc_attrs)]

#![rustc_partition_reused(module="spike_neg2", cfg="rpass2")]
#![rustc_partition_codegened(module="spike_neg2-x", cfg="rpass2")]
#![rustc_partition_codegened(module="spike_neg2-y", cfg="rpass2")] // this is wrong!

mod x {
    pub struct X {
        x: u32, y: u32,
    }

    #[cfg(rpass1)]
    fn make() -> X {
        X { x: 22, y: 0 }
    }

    #[cfg(rpass2)]
    fn make() -> X {
        X { x: 11, y: 11 }
    }

    pub fn new() -> X {
        make()
    }

    pub fn sum(x: &X) -> u32 {
        x.x + x.y
    }
}

mod y {
    use x;

    pub fn assert_sum() -> bool {
        let x = x::new();
        x::sum(&x) == 22
    }
}

pub fn main() {
    y::assert_sum();
}