From 4d56d07c051bc73e91cd94a19102f2d68491c350 Mon Sep 17 00:00:00 2001 From: eggyal Date: Wed, 11 Sep 2019 09:55:08 +0100 Subject: [PATCH] Correction --- text/000-prototypal-inheritance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/000-prototypal-inheritance.md b/text/000-prototypal-inheritance.md index 1548d7a..ec14301 100644 --- a/text/000-prototypal-inheritance.md +++ b/text/000-prototypal-inheritance.md @@ -49,7 +49,7 @@ There are three key problems with the status quo that currently prevent exported This RFC proposes a solution to all of these points, and furthermore also proposes a solution to the related problem of obtaining a [`JsValue`](https://rustwasm.github.io/wasm-bindgen/api/wasm_bindgen/struct.JsValue.html) for any given export or import which could be used, for example, to pass a `struct` to a JS API that expects a constructor function (such as [`web_sys::CustomElementRegistry::define`](https://rustwasm.github.io/wasm-bindgen/api/web_sys/struct.CustomElementRegistry.html#method.define)). -These problems are addressed in this order below, but consideration is at first only given to how exported types are instantiated from JavaScript; the problem of correctly instantiating exported types from within WASM is not visited until the third section (on FFI polymorphism). +These problems are addressed in this order below, but consideration is at first only given to how exported types are instantiated from JavaScript; the problem of correctly instantiating exported types from within WASM is not visited until the end. ### Generating `extends` clause in shim classes