Gary Burgess

I'm not so sure you'll be able to do that without an `Iso`, since state mapping is invariant: https://github.com/purescript-halogen/purescript-halogen/blob/dd301747260620946956048a86e07e9efe1b6380/src/Halogen/Query/HalogenM.purs#L210-L229 There was some tangentially related discussion in #645 that means that...

What, [like this](https://github.com/purescript/documentation/blob/master/guides/FFI-Tips.md#avoid-directly-calling-ps-code-from-foreign-modules)? :smile:

Agreed it should be more prominent / perhaps expanded though.

It's under "FFI Tips" rather than just "FFI" in the guides, we should probably consolidate them :)

@JordanMartinez It's not so much I want to redo `Foreign`, it's that I don't think the current library should exist, or perhaps not in core at least. 1. it only...

It'd be better if we can auto-polyfill this or something, since `imul` does not have solid browser support. It's not even ES5, nevermind the currently-supported ES3. 😕

Only that it doesn't fix `(*)` for integers.

The `driver-io` example is probably a better case if you're just trying to figure out how to work with the `HalogenIO` returned from `runUI`. This example was probably of more...

Just curious, since you seem to have a few questions about `runUI` related things, have you read the [relevant part of the guide](https://purescript-halogen.github.io/purescript-halogen/guide/06-Running-Application.html#using-halogenio) on it? Are there things in there...

No, there's nothing like that. There is a library that provides string rendering for the Halogen VDOM (https://github.com/slamdata/purescript-halogen-vdom-string-renderer), but it's only had very light use.