dimensionalOS / dimensionalOS/dimos
No cross-language way to define a custom message
Open
Nobody has claimed this yet.
core
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
There is no standard guide or mechanism for defining a custom message type that python, rust, and C++ all agree on, so custom types end up python-only (see DIM-836). We need one definition source plus codegen for every language, documented as the blessed path.
Synced from DIM-1469 by jeff
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing DIM-836 and identifying the project’s current message definitions and code-generation entry points for Python, Rust, and C++. Done means one definition source produces compatible custom message types for all three languages, with the blessed workflow documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python, rust
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100