Open
Description
I would like to add a, at least partial, language implementation for Rune, an embeddable dynamic programming language for Rust. I feel fairly confident that I could at the very least implement a ScriptHost
and an ApiProvider
for it.
Other than the what's listed in this comment, is there anything else I should keep in mind when adding a new language implementation?
Metadata
Metadata
Assignees
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
makspll commentedon Jan 17, 2024
Hi, a Rune implementation would be very welcome, I'd reccomend doing this in small chunks, starting with a
ScriptHost
only, then a small customApiProvider
and then eventually fully fledged out macros (but I'd delay big API work untill https://github.com/makspll/bevy_mod_scripting/tree/feature/derive_macros hits the main branch :) )[-]Rune Language Implementation [/-][+]Rune - Proxy macros[/+]makspll commentedon Apr 5, 2024
Renaming since the first level of support was achieved
[-]Rune - Proxy macros[/-][+]Support Rune[/+]makspll commentedon Feb 1, 2025
Rune was put on pause for 0.9.0, but once it's reimplemented, it will easilly be able to have the bevy bindings supported