3 ms·
Sorry, I meant the Koto language and built-in library compatibility story. Whats on the roadmap for a 1.0 and will you allow a 2.0? One of my annoyances with Tc
by epage 2y ago
Sorry, I meant the Koto language and built-in library compatibility story. Whats on the roadmap for a 1.0 and will you allow a 2.0? One of my annoyances with Tcl and Lua is their breaking changes would be pushed into my application and I'd have to decide what version of the language to target and have a plan for changing it.
I'm fine with the Rust API breaking compatibility.
- irh 2y agoI can't imagine wanting a 2.0 release, I'd rather take longer to get to 1.0 to reduce the risk of needing it, and anyway I'd much prefer to aim for something like Rust's editions, allowing the language to evolve without the whole community needing to migrate. Before 1.0 I'd want to address at least: - the FFI / package management topics mentioned above - async support: https://github.com/koto-lang/koto/issues/277 https://github.com/koto-lang/koto/issues/277 - extend the parser to support an autoformatter: https://github.com/koto-lang/koto/issues/286 https://github.com/koto-lang/koto/issues/286 ...and then have a larger number of people using it in projects without major issues coming up for a good while, e.g. a year+.