Ooh, I'd never heard of that pattern! After some reading, my worry is that it would damage IDE indexing and/or stack traces due to all the runtime-generated types in a given class hierarchy. It also feels mostly like inheritance instead of composition (which I've become fond of since escaping Java).

I'm creating a binary data interchange format (www.codas.dev) that generates bindings for JS/TypeScript/Rust/Python. Although my biggest gripe is JS' lack of struct-like enums--which is fixable with quirky generated APIs--I'd love traits to more expressively compose different types' binary codecs.

Patterns and their idioms. Almost every coding language can do the same things. The difference is how their creators prioritized those things.

For example: In #python, we use classes and inheritance (“a Duck is a Bird”), whereas in #rust we use compositions of structures (“a Duck has Wings”).

P.S., could I be added to the list too? ❤️

@rosmo.bsky.social this is probably what you're looking for: github.com/Open-STEM/XR....

My startup (www.alicorn.systems) has worked with the WPI XRP and Google Blockly teams in the past--although it's been a minute.