[opam-commits] Passed: gares/opam-repository#32 (release-elpi-1.9.0 - 76918a7)
builds at travis-ci.org
Tue Jan 7 16:38:04 GMT 2020
Build Update for gares/opam-repository
Duration: 14 mins and 49 secs
Commit: 76918a7 (release-elpi-1.9.0)
Author: Enrico Tassi
Message: [new release] elpi (1.9.0)
- `typeabbrev` declarations are now taken into account and unfolded
by the compiler. The type checker refolds abbreviations
when printing error messages with the following caveat: when two type
abbreviations can be refolded the last declared one wins.
- `@macro` are no more accepted in types, since `typeabbrev` provides the
- fix clash between builtin names and type names
- `accumulate` is idempotent: accumulating the same file a second time
has no effect.
- built in predicate are allowed to not assign (not produce a value) for
output and input-output arguments.
- input-output arguments are forced to be `Conversion.t` of type `'a ioarg`,
and recommended to wrap any nested type not able to represent variables
in `ioarg`. Eg `int option` should be `int ioarg option ioarg`. In this
way one can safely call these builtins with non-ground terms, such as
`some _`, for example to assert the result is not `none` but without
providing a ground term such as `some 3`.
- `MLData` declarations for `OpaqueData` are no more named using a macro
but rather using a type abbreviation. This can break user code. The fix
is to substitutie `@myopaquetype` with `myopaquetype` everywhere.
- `diagnostic` data type to be used as an `ioarg` for builtins that can fail
with a relevant error message. On the ML side one can used `Elpi.Builtin.mkOK`
and `Elpi.Builtin.mkERROR "msg"` to build its values.
- `std.assert-ok!`, `std.forall-ok`, `std.do-ok!`, `std.lift-ok` and
`std.while-ok-do!` commodity predicates.
- All operators for `calc` (infix `_ is _`) now come with a type declaration.
View the changeset: https://github.com/gares/opam-repository/compare/a8bef00e66e8^...76918a78c443
View the full build log and details: https://travis-ci.org/gares/opam-repository/builds/633846743?utm_medium=notification&utm_source=email
You can unsubscribe from build emails from the gares/opam-repository repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=12544626&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Opam-commits