Skip to content
Commits on Jun 30, 2011
  1. [feature] parser: allowing slicing annotations on local functions

    Valentin Gatien-Baron committed
  2. [cleanup] open: remove Base in opalang

    Raja committed
  3. [cleanup] Base: remove sprintf

    Raja committed
  4. [cleanup] Base: remove error

    Raja committed
Commits on Jun 27, 2011
  1. @fpessaux

    [fix] stdlib: Ticket OPA-608. Value restriction issue no CSS.

    fpessaux committed
    The origin of the problem is that
      id_gui_area = "foo"
      default_css = css #{id_gui_area} { } ;
    is rewritten into an application expression. so it is considered expansive
    and can't be generalized. The type of the expression is
      ordered_map(Css.entry, map(string, 'v0), Css.order)
    with the 'v0 being not generalizable.
    In fact, the deeper issue is the fact that we are not able to write
    in Opa the type of Map_make showing the type of values of the map.
    So we are not able to force these values to have a constrained type.
    We would like to be able to have a "'value Map('key, 'order)" or
    something like that.
    So, to workaround, we added a field to the module Css_private and a
    constraint on this field stating that values are of type
    list(Css.prop_value_item). Hence, this constraint gets propagated and
    the type of the module contains no more type variables.
    The added field "renames" (is an alias on) the field "empty" of maps and
    is the one used in parsers_utils.trx to rewrite CSS constructs.
Commits on Jun 22, 2011
  1. [update] parser: the rules for parser expr and types were broken

    Valentin Gatien-Baron committed
    for quite some time, actually
Commits on Jun 21, 2011
  1. Initial open-source release

    MLstate committed
Something went wrong with that request. Please try again.