3 ms·
Rather than having independent language implementations of LIVR which can diverge, stop being maintained etc. etc. What about having a common description of th
by CraigJPerry 6y ago
Rather than having independent language implementations of LIVR which can diverge, stop being maintained etc. etc.
What about having a common description of the supported behaviours then compile these to each supported language? Like AWS generates its language bindings
API descriptions: https://github.com/aws/aws-sdk-js/tree/master/apis https://github.com/aws/aws-sdk-js/tree/master/apis
https://awsfeed.com/whats-new/open-source/generate-python-java-and-net-software-libraries-from-a-typescript-source https://awsfeed.com/whats-new/open-source/generate-python-ja...
- dangoor 6y agoIsn't this essentially an implementation detail? For example, there could be a tool that takes LIVR spec as input and generates nicely typed Go could that returns properly validated input?