Sounds like great timing. See if it can help.

Amazing timing. I was going to build a JSON-RPC in the next few weeks. Will see if I can make use of this.

Doing dynamic dispatching in a strict static typing language is hard. Something as simple as,<pre><code> map.put(&quot;add&quot;, add);
 map.put(&quot;hello&quot;, hello);

 fn add(a: i32, b: i32) i32 { return a + b; }
 fn hello() []const u8 { return &quot;Hello World&quot;; }
</code></pre>
is impossible because the value type of key&#x2F;value of the map needs to be the same but all the function types are different. Calling functions with different number of parameters, different parameter types, and different return type dynamically is difficult.Other languages either use dynamic typing, runtime reflection, macro, or passing in one big generic parameter and let the function figure it out.In ZigJR, I use Zig&#x27;s comptime feature to do compile time reflection to figure out a function&#x27;s parameter types, return types, and return errors. I package them up into a specific call object and use the interface pattern to produce a uniformly typed object to be put into the map. It&#x27;s not easy but doable. [1][1] <a href="https:&#x2F;&#x2F;github.com&#x2F;williamw520&#x2F;zigjr&#x2F;blob&#x2F;master&#x2F;src&#x2F;rpc&#x2F;json_call.zig">https:&#x2F;&#x2F;github.com&#x2F;williamw520&#x2F;zigjr&#x2F;blob&#x2F;master&#x2F;src&#x2F;rpc&#x2F;jso...</a>

Show HN: I built a JSON-RPC library for Zig with compile time reflection