tvcutsem

/*
 * Horton in JavaScript: delegation with blame attribution in an object-capability language
 *
 * See http://erights.org/elib/capability/horton/index.html for idea and paper.
 *
 * Implementation based on: http://erights.org/elib/capability/horton
 * (with N-ary message support, lexical nesting and rights amplification)
 *
 * To run:
 *

mhofman

export declare class Wrapper<Kind, Value = any> {
  private kind: Kind;
  private value: Value;
}

export interface WrapperRegistry<Kind> extends Function {
  constructor: WrapperRegistryConstructor;
  wrap<T>(value: T): Wrapper<Kind, T>;
  unwrap<T>(wrapped: Wrapper<Kind, T>): T;
}

jfparadis

trace(`Compartment imported\n`);

const XSCompartment = globalThis.Compartment;
trace('Compartment.map: ' + Object.keys(XSCompartment.map)+'\n');

// Mappin utility function.
// Create the child XS map from the parent XS map.
function createXSMap(modules) {
  // Need to at least allow new compartments to be created.
  const result = { Compartment: XSCompartment.map.Compartment };

rossberg

# Reference Types for WebAssembly

## Introduction

Use cases:

* Easier and more efficient interop with host
* Manipulation of tables inside Wasm
* Tyoed function pointers
* Setting the stage for other proposals like exception handling

dead-claudia

Edit: The proposal now lives here, and this below is generally out of date.

---

Non-linear Control Flow

Asynchrony is hard. Modeling it is not super intuitive in most languages, JavaScript being no exception for the longest time. But we have been making progress:

1. Callbacks give us the base concept, thanks to lambda calculus.

dead-claudia

// Non-blocking async iterators + Angular 1
function searchWikipedia(term) {
    return $http({
        url: "http://en.wikipedia.org/w/api.php?&callback=JSON_CALLBACK",
        method: "jsonp",
        params: {
            action: "opensearch",
            search: encodeURI(term),
            format: "json"
        }

domenic

Redirecting GitHub Pages after a repository move

The problem

You have a repository, call it alice/repo. You would like to transfer it to the user bob, so it will become bob/repo.

However, you make heavy use of the GitHub Pages feature, so that people are often accessing https://alice.github.io/repo/. GitHub will helpfully redirect all of your repository stuff hosted on github.com after the move, but will not redirect the GitHub Pages hosted on github.io.

The solution

erights

const makeAddr = (x => (y => x + y));

const wm = makeWeakMap();

const makeAddr = (x => {
  const fn = (y => x + y);
  wm.set(fn, {get x() { return x; });
  return fn;
});

caridy

Updated (Aug 2nd, 2016)

API Refinements:

• The default global scope when creating a new realm has no extra capabilities, it is confusing, we can remove it.
• The realm object is the real power object, and users can decide to share it or not via endowments.
• In a realm, you can create as many global scopes as you want via realmObj.createNewGlobalScope().
• No more proxy-like API at the realm level, if you want to proxy a global, that should be used when creating a new global scope.

The API proposal:

domenic

var p0 = Promise.cast(null);
var p1 = p0.then(() => remotePromise);
var p2 = p1.invoke("foo");

line 2 calls remotePromise's .then method, like so:
  remotePromise.then(v => { set p1's [[Value]] to v }, r => { set p1's [[Reason]] to r })
it ALSO stores remotePromise in [[Following]]

Once remotePromise settles, i.e. once one of the two above callbacks gets called,
[[Following]] gets cleared.