🚧 Work in progress
Currently, Genotype can be only installed from source code using Cargo:
cargo install genotype_cliThe current goal is to ship v0.1. There's an immediate need for Genotype in the projects I'm working on, so the first version would include everything to start using it in production. Namely:
- Literals support
- Rust target
- Documentation generation
- Complete package generation
- Tagging/mapping support
- Annotations to precisely define int/float types
- Errors reporting
The design principles are presented in the order of importance.
Both the syntax and the described structures should be unambiguous.
While the syntax should limit ambiguity as much as possible, complete unambiguity should be achieved by the type system.
Data structures should be portable and representable in JSON.
Genotype data structures should visually map to the data representation. It should be obvious what the JSON would look like.
It should be possible to express any structure in any target language. This means that not all target language structures can be necessarily expressed in Genotype, but any Genotype structure can be expressed in any target language.
The resulting target language code should be idiomatic and consider the context where the target language is used.
Genotype aims to be as expressive as possible while maintaining idiomaticity and compatibility with the target languages.
Genotype should not be dogmatic and lean into practicality when necessary.
The target language code should stay relevant for as long as possible. This means limiting the use of dependencies.