Calling messages by string and message families
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 693
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
This is technically possible, but seems way to risky. Minor user mistakes would lead to terrible ub, crashes, or worse.
It is possible to have some kind of safety for such a feature?
Perhaps this should be left for message families: a hypothetical new feature which groups all messages with the same signature as a "family". Then calling by string would be safe. A family would be a good way to expose messages to a language like lua or js.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the existing message-calling API and its handling of string names, then determine whether message families are a defined project concept. Done would require an agreed safety design and documented behavior for string calls and language bindings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, javascript, lua
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100