b65127c2cb
* Rename `HashMapConfiguration` to `HashMapContext` * Rename `EmptyConfiguration` to `EmptyContext` * Implement `Context` for both predefined contexts * Add the `ContextNotManipulable` error variant * Add function `EvalexprError::expected_type` to emit a specific type error when a type is expected dynamically within a context * Update tests and doctests * Add ValueType enum to aid dynamic typing Relates to #22
1.4 KiB
1.4 KiB
Change Log
Unreleased
Added
- Add the
Context
trait, that is a manipulable configuration - Add
ContextNotManipulable
error variant for theEmptyContext
Removed
Changed
- Get rid of some unwraps to improve safety
- Rename
HashMapConfiguration
toHashMapContext
andEmptyConfiguration
toEmptyContext
Fixed
Deprecated
1.2.0 - 2019-03-23
Added
- Add
serde
feature - Implement
serde::de::Deserialize
forNode
- Document
serde
usage - Add custom error type with a
String
message
Changed
- Highlighting in documentation
1.1.0 - 2019-03-20
Added
- Internal aliases
IntType
andFloatType
used by theValue
enum are now public - Type alias
TupleType
used to represent tuples was added - Error types like
Error::ExpectedInt
for expecting each value type were added - Shortcut functions like
eval_int
oreval_int_with_configuration
to evaluate directly into a value type were added - Documentation for the shortcut functions was added
- Functions to decompose
Value
s were added and documented
Removed
- Integration tests were removed from shipped crate
Fixed
- Wording of some documentation items was changed to improve readability
1.0.0 - 2019-03-20
- First stable release