- 09 8月, 2015 1 次提交
-
-
由 Sean McArthur 提交于
-
- 29 7月, 2015 1 次提交
-
-
由 Oliver Schneider 提交于
-
- 09 7月, 2015 1 次提交
-
-
由 Esption 提交于
-
- 08 7月, 2015 1 次提交
-
-
由 Esption 提交于
-
- 04 7月, 2015 5 次提交
-
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
- 28 6月, 2015 1 次提交
-
-
由 Jared Roesch 提交于
This first patch starts by moving around pieces of state related to type checking. The goal is to slowly unify the type checking state into a single typing context. This initial patch moves the ParameterEnvironment into the InferCtxt and moves shared tables from Inherited and ty::ctxt into their own struct Tables. This is the foundational work to refactoring the type checker to enable future evolution of the language and tooling.
-
- 26 6月, 2015 1 次提交
-
-
由 Eduard Burtescu 提交于
-
- 13 6月, 2015 1 次提交
-
-
由 Eli Friedman 提交于
Use camel-case naming, and use names which actually make sense in modern Rust.
-
- 11 6月, 2015 1 次提交
-
-
由 Joshua Landau 提交于
-
- 10 6月, 2015 1 次提交
-
-
由 Eduard Burtescu 提交于
-
- 16 5月, 2015 1 次提交
-
-
由 Alex Crichton 提交于
Helps prevent mixed content warnings if accessing docs over HTTPS. Closes #25459
-
- 04 5月, 2015 1 次提交
-
-
由 Carol Nichols 提交于
-
- 24 4月, 2015 2 次提交
-
-
由 Sean Patrick Santos 提交于
Functional changes for associated constants. Cross-crate usage of associated constants is not yet working.
-
由 Sean Patrick Santos 提交于
Introduces new variants and types in syntax::ast, middle::ty, and middle::def.
-
- 15 4月, 2015 1 次提交
-
-
由 Tamir Duberstein 提交于
`s/([^\(\s]+\.)len\(\) [(?:!=)>] 0/!$1is_empty()/g`
-
- 04 4月, 2015 1 次提交
-
-
由 Jonathan S 提交于
-
- 03 4月, 2015 1 次提交
-
-
由 Nick Cameron 提交于
Closes #23909
-
- 28 3月, 2015 1 次提交
-
-
由 Richo Healey 提交于
-
- 27 3月, 2015 1 次提交
-
-
由 Alex Crichton 提交于
Now that support has been removed, all lingering use cases are renamed.
-
- 24 3月, 2015 1 次提交
-
-
由 Niko Matsakis 提交于
`[]` on maps to `get` in rustc, since stage0 and stage1+ disagree about how to use `[]`.
-
- 18 3月, 2015 1 次提交
-
-
由 Nick Cameron 提交于
-
- 12 3月, 2015 4 次提交
-
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
- 06 3月, 2015 1 次提交
-
-
由 awlnx 提交于
-
- 03 3月, 2015 1 次提交
-
-
由 Jorge Aparicio 提交于
-
- 26 2月, 2015 1 次提交
-
-
由 Huon Wilson 提交于
The stability check checks the `PublicItems` map when giving errors if there is a #[stable] item with a public contents that doesn't not have its own stability. Without recording this, struct fields and enum variants will not get errors for e.g. stable modules with unmarked functions internally. This is just improving the compiler's precision to give the standard library developers more information earlier. E.g. #![staged_api] #![feature(staged_api)] #![crate_type = "lib"] #[stable(feature = "rust1", since = "1.0.0")] pub struct Foo { pub x: i32 } #[stable(feature = "rust1", since = "1.0.0")] pub mod bar { pub fn baz() {} } Without the patch it gives: test.rs:12:5: 12:20 error: This node does not have a stability attribute test.rs:12 pub fn baz() {} ^~~~~~~~~~~~~~~ error: aborting due to previous error With the patch it gives: test.rs:7:9: 7:15 error: This node does not have a stability attribute test.rs:7 pub x: i32 ^~~~~~ test.rs:12:5: 12:20 error: This node does not have a stability attribute test.rs:12 pub fn baz() {} ^~~~~~~~~~~~~~~ error: aborting due to 2 previous errors
-
- 24 2月, 2015 8 次提交
-
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-