Yes they do. But
Now here’s the interesting part. The reason
runis a wrapper in the first place is it do some extra things to make sure this function is idempotent, and it communicates elsewhere to store the state of the returned function.
So run/2, run/3 will be doing stuff around the user provided function, which would cause a round trip over the wire.
That means when the data comes back as JSON and is deserialized, the type information is basically lost.
Note
I’m skipping a lot of internal details of why making the round trip over the wire, but that’s basically a requirement (at least at this point in time).
