Tags: anoma/geb
Tags
V0.3.2 Release
The total change set for this release is
* User Facing Changes
- _Lambda Changes_
- Added an error node so that users can express failure
+ This is translated into a maybe type internally for now, and
affects the compilation downwards.
* Bug Fixes
- =Gapply= (the interpreter) now works correctly for the BITC in the
=SWAP= case.
- Fix an issue where higher order functions in the Lambda frontend
would generate incorrect logic when extracting to the core category
** Internal
- The pipeline extractor now properly takes the input stream given to it
- The Vamp-IR extractor function now properly accepts null streams
* Internal Changes
- A maybe function now exists generically throughout the codebase,
allowing one to maybe any object type. See Maybe in the Generics
section of the documentation.
Release 0.3.0
* User Facing Changes
- _Lambda Changes_
1. Types are no longer required on all terms
2. Application and Lambda now take multiple arguments, and expect
arguments uncurried
- _Core Category Changes_
+ Opaque types now extend the core category
- An interpreter now can be used from any category of the codebase
- Cleaner Code generation, through the new BITC backend.
* Bug Fixes
- Geb to Poly had a few bugs fixed in injection, and pair
representations
- Geb no longer exhausts the stack when trying to generate out
vampir for basic circuits.
* Internal Changes
- Reference extensions allow factoring out common parts, not used
outside of poly.
- _We now have the following generic modules_
1. =GEB.GENERICS= - which hosts all generic transformations
2. =GEB.EXTENSION= - which holds all extensions
- We have streamlined the package loading order.
PreviousNext