All Versions
15
Latest Version
Avg Release Cycle
84 days
Latest Release
1106 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v0.12.4 Changes
March 18, 2020- ๐ Fixes an issue with new macros requiring types to be copy.
-
v0.12.3 Changes
March 17, 2020- ๐ Improved macro syntax:
- Object
"key" => value
pair can be now written as either"key": value
orkey: value
without quotes, as long askey
is an identifier. - If you want to use the value of the a variable as a key in the new notation, use
[foo]: value
. - When nesting objects or arrays, it's no longer necessary to use invoke
array!
orobject!
from within another macro. null
is a keyword inside of either macro.- This is a backwards compatible change, although mixing notations within a single macro invocation is not permitted.
- Object
Example
Instead of:
let obj = object! { "foo" =\> array![1, 2, json::Null], "bar" =\> 42};
You can now write:
let obj = object! { foo: [1, 2, null], bar: 42};
- ๐ Improved macro syntax:
-
v0.12.2 Changes
March 11, 2020 -
v0.12.1 Changes
January 14, 2020 -
v0.12.0 Changes
September 06, 2019- โก๏ธ Updated to edition 2018.
- Simplified reading escaped unicode in strings a bit.
- Provided
From<&[T]>
implementation forJsonValue
whereT: Into<JsonValue>
(closes #160). object!
andarray!
macros will no longer re-allocate (closes #159).object!
andarray!
macros can be now used without being imported into local scope (by usingjson::object!
orjson::array!
, thanks @matthias-t).- ๐ฅ BREAKING
HashMap
andBTreeMap
conversions are now more generic, working for any pair ofK
key andV
value whereK: AsRef<str>
andV: Into<JsonValue>
. This means that type inference won't always work in your favor, but should be much more flexible. - You can now
.collect()
an interator of(K, V)
(with bounds same as point above) into anObject
.
-
v0.11.13 Changes
January 17, 2018- ๐ Fixes an overflow that lead to a panic in extremely large integers (see issue #139).
-
v0.11.12 Changes
November 10, 2017- ๐ Optimized away unnecessary copying in the parser stack machine, should result in parsing performance increased by up to 20%.
-
v0.11.11 Changes
November 10, 2017 -
v0.11.10 Changes
October 07, 2017 -
v0.11.9 Changes
July 28, 2017