- 09 9月, 2014 1 次提交
-
-
由 Jonas Hietala 提交于
Closes #12794
-
- 04 9月, 2014 1 次提交
-
-
由 Joseph Crail 提交于
-
- 30 8月, 2014 1 次提交
-
-
由 P1start 提交于
This unifies the `non_snake_case_functions` and `uppercase_variables` lints into one lint, `non_snake_case`. It also now checks for non-snake-case modules. This also extends the non-camel-case types lint to check type parameters, and merges the `non_uppercase_pattern_statics` lint into the `non_uppercase_statics` lint. Because the `uppercase_variables` lint is now part of the `non_snake_case` lint, all non-snake-case variables that start with lowercase characters (such as `fooBar`) will now trigger the `non_snake_case` lint. New code should be updated to use the new `non_snake_case` lint instead of the previous `non_snake_case_functions` and `uppercase_variables` lints. All use of the `non_uppercase_pattern_statics` should be replaced with the `non_uppercase_statics` lint. Any code that previously contained non-snake-case module or variable names should be updated to use snake case names or disable the `non_snake_case` lint. Any code with non-camel-case type parameters should be changed to use camel case or disable the `non_camel_case_types` lint. [breaking-change]
-
- 28 8月, 2014 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 22 8月, 2014 1 次提交
-
-
由 Austin Bonander 提交于
-
- 20 8月, 2014 4 次提交
-
-
由 Tshepang Lekhonkhobe 提交于
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
[breaking-change]
-
- 12 8月, 2014 1 次提交
-
-
由 Luqman Aden 提交于
-
- 01 8月, 2014 1 次提交
-
-
由 Andrew Poelstra 提交于
A quick and dirty fix for #15036 until we get serious decoder reform. Right now it is impossible for a Decodable to signal a decode error, for example if it has only finitely many allowed values, is a string which must be encoded a certain way, needs a valid checksum, etc. For example in the libuuid implementation of Decodable an Option is unwrapped, meaning that a decode of a malformed UUID will cause the task to fail. Since this adds a method to the `Decoder` trait, all users will need to update their implementations to add it. The strategy used for the current implementations for JSON and EBML is to add a new entry to the error enum `ApplicationError(String)` which stores the string provided to `.error()`. [breaking-change]
-
- 30 7月, 2014 1 次提交
-
-
由 Erick Tryzelaar 提交于
-
- 19 7月, 2014 1 次提交
-
-
由 Luqman Aden 提交于
-
- 17 7月, 2014 2 次提交
-
-
由 Nick Cameron 提交于
-
由 Ilya Dmitrichenko 提交于
- add one simple example of using `ToJson` trait - make example code more readable
-
- 16 7月, 2014 1 次提交
-
-
由 Adolfo Ochagavía 提交于
Use `String::from_utf8` instead [breaking-change]
-
- 09 7月, 2014 1 次提交
-
-
由 Richo Healey 提交于
[breaking-change]
-
- 05 7月, 2014 3 次提交
-
-
由 Erick Tryzelaar 提交于
-
由 Erick Tryzelaar 提交于
This significantly speeds up encoding json strings.
-
由 Erick Tryzelaar 提交于
-
- 04 7月, 2014 1 次提交
-
-
由 Patrick Walton 提交于
This was parsed by the parser but completely ignored; not even stored in the AST! This breaks code that looks like: static X: &'static [u8] = &'static [1, 2, 3]; Change this code to the shorter: static X: &'static [u8] = &[1, 2, 3]; Closes #15312. [breaking-change]
-
- 01 7月, 2014 6 次提交
-
-
由 Adolfo Ochagavía 提交于
-
由 Adolfo Ochagavía 提交于
Fixed some errors, removed some code examples and added usage of the `encode` and `decode` functions.
-
由 Adolfo Ochagavía 提交于
-
由 Adolfo Ochagavía 提交于
Now you can just use `json::encode` and `json::decode`, which is very practical **Deprecated `Encoder::str_encode` in favor of `json::encode`** [breaking-change]
-
由 Adolfo Ochagavía 提交于
-
由 Adolfo Ochagavía 提交于
* Tried to make the code more idiomatic * Renamed the `wr` field of the `Encoder` and `PrettyEncoder` structs to `writer` * Replaced some `from_utf8` by `from_utf8_owned` to avoid unnecessary allocations * Removed unnecessary `unsafe` code
-
- 30 6月, 2014 2 次提交
-
-
由 Steven Fackler 提交于
I ended up altering the semantics of Json's PartialOrd implementation. It used to be the case that Null < Null, but I can't think of any reason for an ordering other than the default one so I just switched it over to using the derived implementation. This also fixes broken `PartialOrd` implementations for `Vec` and `TreeMap`. RFC: 0028-partial-cmp
-
由 Patrick Walton 提交于
floating point numbers for real. This will break code that looks like: let mut x = 0; while ... { x += 1; } println!("{}", x); Change that code to: let mut x = 0i; while ... { x += 1; } println!("{}", x); Closes #15201. [breaking-change]
-
- 26 6月, 2014 1 次提交
-
-
由 mrec 提交于
The JSON spec requires that these special values be serialized as null; the current serialization breaks any conformant JSON parser. So encoding needs to output "null", to_json on floating-point types can return Null as well as Number, and reading null when specifically expecting a number should be interpreted as NaN. There's no way to round-trip Infinity.
-
- 25 6月, 2014 1 次提交
-
-
由 Niko Matsakis 提交于
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]
-
- 22 6月, 2014 1 次提交
-
-
由 Erick Tryzelaar 提交于
-
- 18 6月, 2014 1 次提交
-
-
由 Nick Cameron 提交于
Use ty_rptr/ty_uniq(ty_trait) rather than TraitStore to represent trait types. Also addresses (but doesn't close) #12470. Part of the work towards DST (#12938). [breaking-change] lifetime parameters in `&mut trait` are now invariant. They used to be contravariant.
-
- 17 6月, 2014 1 次提交
-
-
由 theptrk 提交于
-
- 16 6月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
-
- 15 6月, 2014 1 次提交
-
-
由 Piotr Jawniak 提交于
-
- 12 6月, 2014 2 次提交
-
-
由 Alex Crichton 提交于
* The select/plural methods from format strings are removed * The # character no longer needs to be escaped * The \-based escapes have been removed * '{{' is now an escape for '{' * '}}' is now an escape for '}' Closes #14810 [breaking-change]
-
由 Alex Crichton 提交于
The following features have been removed * box [a, b, c] * ~[a, b, c] * box [a, ..N] * ~[a, ..N] * ~[T] (as a type) * deprecated_owned_vector lint All users of ~[T] should move to using Vec<T> instead.
-
- 09 6月, 2014 1 次提交
-
-
由 Joseph Crail 提交于
-
- 06 6月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
-