- 15 5月, 2013 6 次提交
-
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
由 Alex Crichton 提交于
-
- 14 5月, 2013 2 次提交
-
-
由 Marvin Löbel 提交于
-
由 Björn Steinbrink 提交于
fail!() used to require owned strings but can handle static strings now. Also, it can pass its arguments to fmt!() on its own, no need for the caller to call fmt!() itself.
-
- 13 5月, 2013 6 次提交
-
-
由 Corey Richardson 提交于
-
由 Luqman Aden 提交于
-
由 Corey Richardson 提交于
When trying to import nonexistent items from existing modules, specify that that is what happened, rather than just reporting "unresolved name".
-
由 Patrick Walton 提交于
-
由 Matthijs Hofstra 提交于
-
由 Matthijs Hofstra 提交于
The default versions (atomic_load and atomic_store) are sequentially consistent. The atomic_load_acq intrinsic acquires as described in [1]. The atomic_store_rel intrinsic releases as described in [1]. [1]: http://llvm.org/docs/Atomics.html
-
- 12 5月, 2013 3 次提交
-
-
由 Corey Richardson 提交于
-
由 Tim Chevalier 提交于
-
由 Tim Chevalier 提交于
In #6319, several people mentioned they ran into a "computing fictitious type" ICE in trans. This turns out to be because some of my recent changes to typeck::check::_match resulted in type errors getting reported with ty_err as the expected type, which meant the errors were suppressed, and typechecking incorrectly succeeded (since the errors weren't recorded). Changed the error messages in these cases not to use an expected type at all, rather, printing out a string describing the type that was expected (which is what the code originally did). The result is a bit repetitive and the proliferation of error-reporting functions in typeck::infer is a bit annoying, but I thought it was important to fix this now; more cleanup can happen later.
-
- 11 5月, 2013 4 次提交
-
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Lenny222 提交于
-
由 Corey Richardson 提交于
-
- 10 5月, 2013 11 次提交
-
-
由 Youngsoo Son 提交于
-
由 Youngsoo Son 提交于
-
由 Huon Wilson 提交于
This check only works for `match`s, the checks (incorrectly) do not run for patterns in `let`s.
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Patrick Walton 提交于
-
由 Corey Richardson 提交于
-
由 Corey Richardson 提交于
Recommendation of @kud1ing
-
由 Corey Richardson 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
as part of an autoslice operation (#6272). Fixes #6272.
-
- 09 5月, 2013 8 次提交
-
-
由 Niko Matsakis 提交于
its own type. Use a bitset to represent built-in bounds. There are several places in the language where only builtin bounds (aka kinds) will be accepted, e.g. on closures, destructor type parameters perhaps, and on trait types.
-
由 Björn Steinbrink 提交于
&str can be turned into @~str on demand, using to_owned(), so for strings, we can create a specialized interner that accepts &str for intern() and find() but stores and returns @~str.
-
由 James Miller 提交于
-
由 Youngmin Yoo 提交于
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
They're still parsed though, to get through bootstrapping.
-