mikros/rust - rust - Gitea.pterpstra.com

Author SHA1 Message Date

Author	SHA1	Message	Date
Patrick Walton	416144b827	librustc: Forbid `..` in range patterns. This breaks code that looks like: match foo { 1..3 => { ... } } Instead, write: match foo { 1...3 => { ... } } Closes #17295. [breaking-change]	2014-09-30 09:11:26 -07:00
Niko Matsakis	9e3d0b002a	librustc: Remove the fallback to `int` from typechecking. This breaks a fair amount of code. The typical patterns are: * `for _ in range(0, 10)`: change to `for _ in range(0u, 10)`; * `println!("{}", 3)`: change to `println!("{}", 3i)`; * `[1, 2, 3].len()`: change to `[1i, 2, 3].len()`. RFC #30. Closes #6023. [breaking-change]	2014-06-24 17:18:48 -07:00
Edward Wang	90449abcb3	Adjust codegen logic for range and guarded arms By carefully distinguishing falling back to the default arm from moving on to the next pattern, this patch adjusts the codegen logic for range and guarded arms of pattern matching expression. It is a more appropriate way of fixing #12582 and #13027 without causing regressions such as #13867. Closes #13867	2014-05-05 20:17:59 +08:00

Patrick Walton

416144b827

librustc: Forbid .. in range patterns.

This breaks code that looks like:

    match foo {
        1..3 => { ... }
    }

Instead, write:

    match foo {
        1...3 => { ... }
    }

Closes #17295.

[breaking-change]

2014-09-30 09:11:26 -07:00

Niko Matsakis

9e3d0b002a

librustc: Remove the fallback to int from typechecking.

This breaks a fair amount of code. The typical patterns are:

* `for _ in range(0, 10)`: change to `for _ in range(0u, 10)`;

* `println!("{}", 3)`: change to `println!("{}", 3i)`;

* `[1, 2, 3].len()`: change to `[1i, 2, 3].len()`.

RFC #30. Closes #6023.

[breaking-change]

2014-06-24 17:18:48 -07:00

Edward Wang

90449abcb3

Adjust codegen logic for range and guarded arms

By carefully distinguishing falling back to the default arm from moving
on to the next pattern, this patch adjusts the codegen logic for range
and guarded arms of pattern matching expression. It is a more
appropriate way of fixing #12582 and #13027 without causing regressions
such as #13867.

Closes #13867

2014-05-05 20:17:59 +08:00

3 Commits