e10614a777
Since the desugaring removed special handling for ranges, the error message changed and so I had to adjust `range-1`. Turns out there was a bug where borrowck was too restrictive in some rare cases of constructing ranges from literals. The `range-2` test enshrined this bug -- now it's adjusted to test a case that's actually wrong.
28 lines
903 B
Rust
28 lines
903 B
Rust
// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
|
|
// file at the top-level directory of this distribution and at
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
// option. This file may not be copied, modified, or distributed
|
|
// except according to those terms.
|
|
|
|
// Test range syntax - type errors.
|
|
|
|
pub fn main() {
|
|
// Mixed types.
|
|
let _ = 0u32..10i32;
|
|
//~^ ERROR mismatched types
|
|
|
|
// Bool => does not implement iterator.
|
|
for i in false..true {}
|
|
//~^ ERROR E0277
|
|
|
|
// Unsized type.
|
|
let arr: &[_] = &[1, 2, 3];
|
|
let range = *arr..;
|
|
//~^ ERROR the trait `core::marker::Sized` is not implemented
|
|
//~| ERROR the trait `core::marker::Sized` is not implemented
|
|
}
|