This is prompted by the potential new RSign contributor via https://gitcoin.co/issue/dckc/RSign/1/1538 . I haven't documented ocap discipline there, but I figured I'd polish up the one here first.
The second commit (a806dd2) is additional editorial work. Let me know if you want it in a separate pull request or something.
For reference: the definition of ocap discipline as Memory safety and encapsulation + Primitive effects only via references is taken from Mark Miller's work; in particular:
His OCaps: Small step from pure objects slide has 3 bullets; when writing the monte intro version of Apr 3, 2016, I combined the 2nd and 3rd based on an academic paper that I can't seem to find just now.
I wonder about citing Miller's 2011 talk in our docs. His SFBW talk might even be better. Or the wikipedia article. Or https://github.com/dckc/awesome-ocap . Hm.
fixes #2
This is prompted by the potential new RSign contributor via https://gitcoin.co/issue/dckc/RSign/1/1538 . I haven't documented ocap discipline there, but I figured I'd polish up the one here first.
The second commit (a806dd2) is additional editorial work. Let me know if you want it in a separate pull request or something.
For reference: the definition of ocap discipline as Memory safety and encapsulation + Primitive effects only via references is taken from Mark Miller's work; in particular:
His OCaps: Small step from pure objects slide has 3 bullets; when writing the monte intro version of Apr 3, 2016, I combined the 2nd and 3rd based on an academic paper that I can't seem to find just now.
I adapted it for JavaScript and python in the July 21 version of CONTRIBUTING for rchain-dbr. I filtered out the python stuff Oct 12 in CONTRIBUTING for rmem.
I wonder about citing Miller's 2011 talk in our docs. His SFBW talk might even be better. Or the wikipedia article. Or https://github.com/dckc/awesome-ocap . Hm.