Giter VIP home page Giter VIP logo

maetning's Introduction

Mætning

This is an experiment in using the inverse method as an engine for disproving non-theorems.

  1. Prerequisites

  • Recent OCaml toolchain (programmed using 4.02.1)
  • OCaml Batteries Included (opam install batteries)
  • Menhir (opam install menhir)
  1. Building

Run make from the topmost directory.

The binary will be called maetning.native. Depending on your operating system, you may need to rename it to maetning.exe in order to run it.

maetning's People

Contributors

chaudhuri avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar

maetning's Issues

Rules that create new variables break saturation

@tausbn notes:

A second problem [...] comes from my attempt at creating a goal that would create unboundedly many variables during proof search:

%positive p.
%positive q.

%assume r : (\A y,a,b,w. q(y,a) * q(a,b) * p(b,w)) => (\A z. q(y,z) * p(z,w)).

%refute \E x,y,z. p(x,y) * q(y,z) * p(z,x).

Quiescence issue with new_rules

@tausbn notes:

[I]n some cases, saturation doesn't happen (through what appears to be a problem with the implementation).

An example of this is the following:

%negative nat.
%assume nz : nat(z).

% assume ns : \A x. nat(x) => nat(s(x)).
%assume nns : \A x. nat(x) & nat(x) => nat(s(x)).

%pseudo p : \A x. nat(s(s(s(x)))).

%refute \A x. nat(x) + (nat(x) => 0).

Here, the goal is refutable with the axiom ns, but not with the axiom nns. Since the only difference between these is the fact that the latter requires two instances of the same nat(x), this is somewhat worrisome. I imagine this might be some failure of fairness.

Strange behaviour with quantifiers and negation.

Given

%negative p.

the following two queries succeed:

%refute ~((~(\A x. ~p)) & (\A x. ~p)).

%prove  ~((~(p       )) & (p       )).

Since the former is an instance of the latter, this indicates a bug.
Note that

%prove  ~((~(\A x.  p)) & (\A x.  p)).

succeeds, as does

%prove  ~((~(      ~p)) & (      ~p)).

Thus, both quantification and negation are needed to trigger this bug.

Occurs check test done too early

The oc test needs to be done after the joined term has been instantiated, not before.

This order is of course slower, but it is also correct.

Regression test in tests/bug/occurs_check.mg, courtesy of @tausbn.

Invalid EV collapse

This is currently proved but should not be (checked in as tests/excollapse.mg):

%negative p.
%negative q.

%assume a0 : \E x. p(x).
%assume a1 : \E x. q(x).

%prove \E x. p(x) & q(x).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.