rust/src/test/run-pass/one-tuple.rs

// Why one-tuples? Because macros.


pub fn main() {
    match ('c',) {
        (x,) => {
            assert_eq!(x, 'c');
        }
    }
    // test the 1-tuple type too
    let x: (char,) = ('d',);
    let (y,) = x;
    assert_eq!(y, 'd');
}
syntax: Allow 1-tuple expressions This is for greater uniformity (for example, macros that generate tuples). rustc already supported 1-tuple patterns, but there was no way to construct a 1-tuple term. 2013-02-17 17:41:47 -06:00			`// Why one-tuples? Because macros.`

rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 15:13:15 -05:00
testsuite: more `pub fn main` 2013-03-27 11:58:28 -05:00			`pub fn main() {`
syntax: Allow 1-tuple expressions This is for greater uniformity (for example, macros that generate tuples). rustc already supported 1-tuple patterns, but there was no way to construct a 1-tuple term. 2013-02-17 17:41:47 -06:00			`match ('c',) {`
			`(x,) => {`
Use assert_eq! rather than assert! where possible 2013-05-18 21:02:45 -05:00			`assert_eq!(x, 'c');`
syntax: Allow 1-tuple expressions This is for greater uniformity (for example, macros that generate tuples). rustc already supported 1-tuple patterns, but there was no way to construct a 1-tuple term. 2013-02-17 17:41:47 -06:00			`}`
			`}`
rustc: For one-tuples, make parsing and printing the type work and add a test to reflect-visit-data 2013-02-18 19:45:56 -06:00			`// test the 1-tuple type too`
			`let x: (char,) = ('d',);`
			`let (y,) = x;`
Use assert_eq! rather than assert! where possible 2013-05-18 21:02:45 -05:00			`assert_eq!(y, 'd');`
syntax: Allow 1-tuple expressions This is for greater uniformity (for example, macros that generate tuples). rustc already supported 1-tuple patterns, but there was no way to construct a 1-tuple term. 2013-02-17 17:41:47 -06:00			`}`