Define variable-length array type for C
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
Research direction
The issue proposes --no-static-arrays and a user-supplied vector protocol, but names no implementation files or tests. Start by locating the C code-generation templates and deserialization routines, then assess how generated array types are represented. Done would require an agreed design and implementation for variable-length arrays; the issue leaves that design open.
Written by the indexing model from the issue text.
Description
This is a proposal to allow generation of a variable-length array type in C leaving the implementation up to the user.
For example, the standard Quaternion type:
typedef struct
{
/// saturated float32[4] wxyz
float wxyz[4];
} uavcan_si_unit_angle_Quaternion_1_0;
when using the proposed language option of `--no-static-arrays' could be generated like this:
typedef struct
{
/// saturated float32[4] wxyz
float* wxyz;
size_t wxyz_len;
} uavcan_si_unit_angle_Quaternion_1_0;
An alternative, that would be more complex but would require less unsafe pointer magic, is to create a Vector protocol. Something like this:
typedef NunavutVectorType_Float
{
float* data;
size_t length;
size_t max_length;
bool (*resize)(NunavutVectorType_Float*, size_t);
} NunavutVector_Float;
extern NunavutVector_Float* init_nunavut_vector_float(NunavutVector_Float*);
NunavutVector_Float then must be supplied by the user (the linker will enforce this) and the user must provide the resize method which will be called by deserialization routines when Nunavut needs more memory.
This is a half-baked proposal to encourage a discussion. Please comment.
- Dominant language
- Python
- Stars
- 48
- Forks
- 26
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from OpenCyphal/nunavut
-
build and test dependencies
Difficulty 4/5 3-5 days Newbie friendliness 55/100
OpenCyphal/nunavut#419 ·
Maintainers usually reply within 1 day
-
build and test C++ dependencies
Difficulty 4/5 3-5 days Newbie friendliness 50/100
OpenCyphal/nunavut#418 ·
Maintainers usually reply within 1 day
-
build and test Python
Difficulty 4/5 3-5 days Newbie friendliness 45/100
OpenCyphal/nunavut#416 ·
Maintainers usually reply within 1 day
-
C C++ Python
Difficulty 4/5 3-5 days Newbie friendliness 52/100
OpenCyphal/nunavut#414 · 1 comment ·
Maintainers usually reply within 1 day
-
feature under consideration
Difficulty 5/5 Over a week Newbie friendliness 32/100
OpenCyphal/nunavut#413 ·
Maintainers usually reply within 1 day
All issues in OpenCyphal/nunavut
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
py-econometrics/pyfixest#2072 ·
Maintainers usually reply within 1 day
-
~planning docs
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Kromatic-Innovation/athenaeum#3084 ·
Maintainers usually reply within 1 day
-
Bosch Room Thermostat II number entities offer -500 to 3000 °C setpoint limits and a -32768 to 32767 °C outdoor temperaturePossibly taken @zigpy-review-bot claimed this today. Openbot: code audit
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zigpy/zha-device-handlers#5769 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 80/100
R0Y00/Xbox2Windows#254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kludex/python-multipart#375 ·
Maintainers usually reply within 1 day