Petter A. Urkedal

Thanks for the call, I sent a PR proposal.

While I can see the flattened API would also serve as a good simplification, the abstract API has an advantage that it will be possible to support test fixtures. An...

> Indeed, we do not expose the strong stops for the signals used inside Eliom_content.Html5.R. But this is within our control, and I think we should expose them somehow. Sounds...

Now, this would be the easy part, the DOM-document finalizers: [pandom_finalizer.mli](https://github.com/paurkedal/panograph/blob/master/lib/client/pandom_finalizer.mli), [pandom_finalizer.ml](https://github.com/paurkedal/panograph/blob/master/lib/client/pandom_finalizer.ml).

After some reflection on this, I think weak references are not really needed for a satisfactory FPR framework, and by avoiding them, we both solve the memory management issue for...

@dbuenzli Thanks for the background, didn't realize there was already a discussion this summer. > Well, you solve it by going back to manual memory management... True, though a) signals...

> Not sure this is different of what I was proposing, with my ref count thing you only had to do so at the leaves. Internally retain/release is done automatically....

By functional semantics, I think we'd mean elements which are copied as they are inserted into the document. Then we'd need to create a fresh observed leaf signal in the...

I think dune support would be a tremendous help. Judging from my own experience, using manual rules is infeasible. Just getting it to compile is straight forward, but getting the...

@rgrinberg I would like to take you up on that offer in a couple of months when I have more time to spare, but just to get the thoughts going:...