SoftbearStudios / SoftbearStudios/bitcode
Question: Best approach for polymorphic members
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 671
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
This isn't an issue but a question:
I have a struct something like
#[derive(Encode, Decode)]
struct Foo
{
.. members
blah: Box<[Box<dyn T>]>,
}
my current approach is to have a 'serializing' version of this struct like:
struct DynType { type_id: u64, size: u64 }
struct FooFile
{
.. members
blah: &[DynType],
blah_data: &[u8],
}
where blah's values are stored in blah_data and as bitcode-encoded values linearly written into a byte buf
Is this a reasonable approach? Is there a more efficient approach?
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 repository files, tests, or entry points. First clarify whether a concrete polymorphic serialization feature is wanted and define its format and performance requirements; done would require an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100