Release v0.1.1

CHANGELOG.md

@@ -2,9 +2,15 @@
 
 ## v0.1.1
 
+### Highlights
+
+- **Dot-access syntax for maps**: `u.foo` reads a field off a map value, supported at every expression precedence level (including unary and `if` conditions), with a runtime error for missing fields or non-map operands.
+- **`typeof` builtin**: Runtime type introspection for values.
+
+### Improvements
+
 - **Fix**: Map literals (`{ key: value }`) now evaluate to `Value::Map` instead of erroring.
 - **Fix**: Array literals (`[ expr, ... ]`) now evaluate to `Value::Array` instead of erroring.
-- **Dot-access syntax for maps**: `u.foo` reads a field off a map value, supported at every expression precedence level (including unary and `if` conditions), with a runtime error for missing fields or non-map operands.
 
 ## v0.1.0
 

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "flt"
-version = "0.1.0"
+version = "0.1.1"
 edition = "2021"
 description = "a 'lite' functional language"
 license = "MIT"

README.md

@@ -16,7 +16,7 @@ The runtime currently evaluates a subset of that syntax.
 
 ```toml
 [dependencies]
-flt = "0.1.0"
+flt = "0.1.1"
 ```
 
 ## Quick start

docs/README.md

@@ -14,4 +14,4 @@ This folder contains initial documentation for the `flt` language as it exists i
 
 ## Scope
 
-These docs describe the currently implemented parser and CLI evaluator for version `0.1.0`.
+These docs describe the currently implemented parser and CLI evaluator for version `0.1.1`.

docs/quickstart.md

@@ -11,7 +11,7 @@ cargo run -p flt-cli -- version
 Expected output:
 
 ```text
-flt version 0.1.0
+flt version 0.1.1
 ```
 
 ## Start the REPL

features/cli.feature

@@ -3,4 +3,4 @@ Feature: flt version
   Scenario: flt version
     When the command `flt version` is run
     Then it should exit with status code 0
-    And the output should contain "flt version 0.0.2"
+    And the output should contain "flt version 0.1.1"