Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Question: Best approach for polymorphic members

Open
#91 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
backend

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.

Description

question

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?

Dominant language
Rust
Stars
671
Forks
61
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SoftbearStudios/bitcode

All issues in SoftbearStudios/bitcode

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.