GithubHelp home page GithubHelp logo

behavr's Issues

LGM on LADL proof theory

On Apr 22, he referred me to https://github.com/rchain/pi4u/tree/master/AFreshProofTheoryForLADL :

That’s behind our current work by about 2 weeks. We’re incorporating this paper. That allows us to eliminate most of the contextualized resourced theory, but it has the consequence of adding meta-variables to our type judgments.

i am evaluating Kiama as an input format for the theories LADL takes as input by implementing the rho-combinator paper. The code for this implementation is here.

use case: cell type

from DAO bug typing:

CT( get, set ) = <get( rtn )>?( <rtn>! | CT( get, set ) ) + <set( nv )>?( CT( get, set ) )

I'm not sure how to read that... in particular get( rtn ). Does + mean Mixture / separation? If so, then what does | mean? Does + mean Conjunction???

use case: structured data (XML) from Namespace Logic

using

  • rholang syntax for for quoting (@), lift / send and activity / input
  • SLMC syntax for or, (maxfix X F) and forall

we get:


@(maxfix X
     forall m .
        m!(forall n. 0 or n!(X) or (maxfix Y { forall n' . for(n' <- b){ X or Y} }
              or (X | X ) ) ) 

I used KaTex to get:

$\phi_{info} = \q{ \rec{X} {\forall m . \lift{m}{\forall n. 0 \lor \lift{n}{X} \lor \rec{Y}{\forall n' . \act{n'}{b}{(X \lor Y)} } \lor (X | X ) }} }$

macros:

{
    "\\q": "\\ulcorner #1 \\urcorner",
    "\\lift": "#1 \\langle\\lvert #2 \\rvert\\rangle",
"\\act": "\\langle #1 ? #2 \\rangle #3",
 "\\rec": "\\mathrm{rec} #1 . ( #2 )"
}

rendered

behavioural type system defined (Scalas, Yoshida)

This was sort of news to me:

Our new MPST theory is a case of behavioural type system: it treats types as
simple processes that reduce and evolve along a typed computation; and since types are simpler
than programs, they can be analysed with simpler methods (e.g., finite model checking via our
parameter φ, cf. ğ6).

found via https://lobste.rs/t/formalmethods

cc @tgrospic @leithaus

rhocaml structurallyEquivalent bug?

0 | @0!(0) | @0!(0) is equivalent to (0 | @0!(0)) | @0!(0) right?

both are equivalent to @0!(0) | @0!(0)

Either my transcription to scala is wrong or there's a bug in rhocaml.

use case: DAO bug

Also from DAO bug typing:

type TB  = <getBalance>?( <rtn>! | TB )
  + <deposit>?( <ackDeposit>?TB )
  + <users.keys>( <ackWithdraw>?TB + <ackSend>?TB )

The line above says "... we simply disjoin the types of each case ..." which tells us how to read +. But logic.ml doesn't have disjunction. Ah... SLMC does:

| Or of formastnode * formastnode

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.