Metadata revisions for exference-1.6.0.0

Package maintainers and Hackage trustees are allowed to edit certain bits of package metadata after a release, without uploading a new tarball. Note that the tarball itself is never changed, just the metadata that is stored separately. For more information about metadata revisions, please refer to the Hackage Metadata Revisions FAQ.

No. Time User Changes
-r4 Tue Aug 1 21:49:06 UTC 2017 lspitzner
  • Changed maintainer from

    Lennart Spitzner <lsp@informatik.uni-kiel.de>
    to
    Lennart Spitzner <hexagoxel@hexagoxel.de>

-r3 Mon Feb 13 15:48:34 UTC 2017 lspitzner
  • Changed source-repository from

     
    source-repository head
        type: git
        location: git@github.com:lspitzner/multistate.git
    to
     
    source-repository head
        type: git
        location: git@github.com:lspitzner/exference.git

-r2 Mon Feb 13 15:46:13 UTC 2017 lspitzner
  • Changed source-repository from

     
    source-repository head
        type: git
        location: git@github.com:lspitzner/exference.git
    to
     
    source-repository head
        type: git
        location: git@github.com:lspitzner/multistate.git

  • Changed description from

    Type inference takes an expression and tells you its type. This process
    can be inversed: We recursively create random expression trees while checking
    that they -so far- match a given input type. At each step we do the backwards
    step of the inference algorithm step. If you are lucky, this search
    yields one or more expressions.
    Djinn is a similar tool that guarantees to always terminate. But the
    cost of that property is that Djinn does not properly handle polymorphic
    queries - and those are the interesting ones, really :)
    Exference supports type classes, handles undeclared types well
    (Foo -> Foo yields id for unknown Foo), does _not_ check kinds,
    can pattern-match on newtypes, supports RankNTypes.
    Exference reads an environment of function types, data types, type classes
    and instances. The user can add to this environment, but keep in mind that
    each addition enlarges the search space.
    to
    Type inference takes an expression and tells you its type. This process
    can be inversed: We recursively create random expression trees while checking
    that they -so far- match a given input type. At each step we do the backwards
    step of the inference algorithm step. If you are lucky, this search
    yields one or more expressions.
    
    Djinn is a similar tool that guarantees to always terminate. But the
    cost of that property is that Djinn does not properly handle polymorphic
    queries - and those are the interesting ones, really :)
    
    Exference supports type classes, handles undeclared types well
    (Foo -> Foo yields id for unknown Foo), does _not_ check kinds,
    can pattern-match on newtypes, supports RankNTypes.
    
    Exference reads an environment of function types, data types, type classes
    and instances. The user can add to this environment, but keep in mind that
    each addition enlarges the search space.

-r1 Mon Feb 13 15:44:08 UTC 2017 lspitzner
  • Changed source-repository from

     
    source-repository head
        type: git
        location: git@github.com:lspitzner/multistate.git
    to
     
    source-repository head
        type: git
        location: git@github.com:lspitzner/exference.git

-r0 Mon Feb 13 15:41:03 UTC 2017 lspitzner