I took the liberty and implemented a quick proof of concept.

The following code, compiled with purescript-static,

Remote.purs

module Remote where

import Static

id_static :: forall a. StaticPtr (a -> a)
id_static = static \x -> x

Test.purs

module Test where

import Control.Monad.Eff
import Control.Monad.Eff.Console

import Prelude
import Static

import Remote

main :: forall eff. Eff (console :: CONSOLE | eff) Unit
main = do
  log $ derefStaticPtr id_static "test_static"

prints out test_static.

Remote.purs generates the following code:

// Generated by purs version 0.11.4
"use strict";
var Static = require("../Static");
var static_ptr_table = {
    static_ptr_0: function (x) {
        return x;
    }
};
var id_static = new Static.StaticPtr("Remote", "static_ptr_0");
module.exports = {
    static_ptr_table: static_ptr_table,·
    id_static: id_static
};

Static pointers can't be defined in the same module in which they are dereferenced right now (hence the separate Remote module), because by the time purescript-static/derefStaticPtrByModule is called the exports table isn't set yet. Also, derefStaticPtrByModule uses the convention used in psc-bundle and looks up the static table in the global PS object. Don't know if e.g. Webpack differs here.

I don't think that issue is particularly hard to solve though. Please let me know if you like the general direction of this.

Uh oh!

Implement static pointers #2869

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions