Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(c++) variable_array_type_include is ignored #277

Closed
thirtytwobits opened this issue Jan 31, 2023 · 0 comments
Closed

(c++) variable_array_type_include is ignored #277

thirtytwobits opened this issue Jan 31, 2023 · 0 comments
Labels
bug Something isn't working major A major issue that should be a priority

Comments

@thirtytwobits
Copy link
Member

Include property is not fetched properly and is therefore ignored. This prevents using std::vector or other container types for variable-length arrays in C++ types.

@thirtytwobits thirtytwobits added bug Something isn't working major A major issue that should be a priority labels Jan 31, 2023
thirtytwobits added a commit to thirtytwobits/nunavut that referenced this issue Jan 31, 2023
This fixes, documents, and covers with test the ability to use std::vector instead of the built-in variable-length array type.

Also got rid of rstcheck as that project seems to be a hot mess. Too many false positives and major bugs not getting fixed. We’ll just have to manually test the docs using the tox -e docs target.
thirtytwobits added a commit to thirtytwobits/nunavut that referenced this issue Jan 31, 2023
This fixes, documents, and covers with test the ability to use std::vector instead of the built-in variable-length array type.

Also getting a head-start on OpenCyphal#224

Also,also got rid of rstcheck as that project seems to be a hot mess. Too many false positives and major bugs not getting fixed. We’ll just have to manually test the docs using the tox -e docs target.
thirtytwobits added a commit that referenced this issue Jan 31, 2023
* Fix for #277

This fixes, documents, and covers with test the ability to use std::vector instead of the built-in variable-length array type.

Also getting a head-start on #224

Also,also got rid of rstcheck as that project seems to be a hot mess. Too many false positives and major bugs not getting fixed. We’ll just have to manually test the docs using the tox -e docs target.

* fixing broken doctest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working major A major issue that should be a priority
Projects
None yet
Development

No branches or pull requests

1 participant