Exciting news, LIGO has released version 1.0! We made sure to fit in this release a number of pending breaking changes, so that our users do not need to catch up with small breaking changes every release, and can handle the migration in bulk. Please continue reading to learn which changes may affect your existing codebase.

See Why did the default datatype layout change to @layout comb ? for background about this change.

When compiling to Michelson, LIGO must choose a "layout" for record and variant data types. Unfortunately, Michelson only has binary pair/or types, for esoteric theoretical reasons.

This means that for each record or variant type, LIGO must pick one of the many isomorphic binary tree structures which can represent it in Michelson. This choice needs to be consistent (else we will get type errors) and ideally it should be flexible (so that users can interoperate with Michelson types defined in standards or emitted by other compilers.)