Under eo-phi-normalizer/data, we have a collection of $\varphi$ programs for testing, versioned by the EO version with which they're compatible. Some of these programs contain $\lambda$-assets, but the "signature" of these atoms can change from one version to another (e.g.: changing param name/count). A CHANGELOG.md should be added to that directory, documenting what atoms changed from one version to the next to make it easier to identify compatibility with unit tests.
It would also be great if a README.md can be added, describing what each atom (latest version) does, perhaps with links to their original implementation in Java.
deemp
commented
2 months ago
Under
eo-phi-normalizer/data, we have a collection of $\varphi$ programs for testing, versioned by the EO version with which they're compatible. Some of these programs contain $\lambda$-assets, but the "signature" of these atoms can change from one version to another (e.g.: changing param name/count). ACHANGELOG.mdshould be added to that directory, documenting what atoms changed from one version to the next to make it easier to identify compatibility with unit tests. It would also be great if aREADME.mdcan be added, describing what each atom (latest version) does, perhaps with links to their original implementation in Java.Useful links: