Look into removing autogen from the build
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 441
- Forks
- 90
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 5
Description
Currently there are only two items generated to build csp engine
- TimeIndexPolicy
- dynamic BasketInfo struct
this complicated the build immensely, and also blocks us from cross compiling: https://github.com/Point72/csp/issues/264
We should see if there is a nice way to define these types in C++ and expose them to python, rather than define them in python and autogen c++
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
Start by tracing how TimeIndexPolicy and the dynamic BasketInfo struct are generated for the C++ build, and review the cross-compiling context in issue #264. Determine whether these types can be defined in C++ and exposed to Python without autogen. Done means the generation path is removed or simplified while the CSP engine still builds and cross-compiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100