Literals, Constraints, and Costs

Literal values

This release adds support for literal values of various special forms. The language already had these notions implied by the specification, but until now we didn't actually have a way to parse them if written as literal values.

• Add unit literals by @istathar technique-lang/specification#12
• Add unit literals by @istathar in #134
• Add response literals by @istathar technique-lang/specification#13
• Add response literals by @istathar in #135
• Add tuple literals by @istathar technique-lang/specification#14
• Add tuple literals by @istathar in #136

Constraints and Resources

Added support for cost as a form of annotation to a Technique step, allowing you to say "this step should be done within X" or "this step costs Y". This is an insight that goes back to the late Peter Miller. He recognized over 10 years ago that this machinery could, very quickly, establish how long a procedure takes and whether its steps were completed in the time they should have been, so we are delighted to have finally a feature that reflects this, in memorium.

• Add time constraints by @istathar in technique-lang/specification#15
• Introduce within keyword by @istathar in #137
• Construction and validation of Cost literals by @istathar in #138
• Fix syntax highlighting when formatting by @istathar in #139

Full Changelog: v0.6.4...v0.6.5