-
Notifications
You must be signed in to change notification settings - Fork 0
Initial code publication #1
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
Conversation
20e16b3
to
29cdfe4
Compare
Signed-off-by: Horolsky <[email protected]>
Signed-off-by: Horolsky <[email protected]>
Signed-off-by: Horolsky <[email protected]>
Signed-off-by: Horolsky <[email protected]>
Signed-off-by: Horolsky <[email protected]>
Signed-off-by: Horolsky <[email protected]>
29cdfe4
to
f6a52e2
Compare
7813cf2
to
8faf320
Compare
Generate API reference with local doxygen outside of the Bazel build TODO: remove after #6
* Refine namespaces and move internals into detail ns * Remove redundant traits and metafuncs * Move precise template to decor ns * Add doxygen docs. Some trivial metafuncs omitted. * Refactor few templates Breaking: * Move json_from and dejsonize from reflect to main ns
dadb352
to
73d458d
Compare
Move * packages/cxx => zmbt-framework/backends/cxx * packages/py => zmbt-framework/cli
General note: |
@Klanor Many internal classes are in prototype state and will be refactored before MS3 with the support of static checkers. |
Oye, @zenseact/beltalowda, @Klanor , I've added the strategy for prototype code refinement to the pr description. |
3f3ecc6
to
02e9dcc
Compare
02e9dcc
to
a5a897d
Compare
Add doxygen docs to Environment interfaces and update docs/environment.md. Interfaces for internal functionality left undocumented - they should be separated from the API in future.
- Fix code generation issues - Fix aliases for bitwise ops - add U+00D7 alias for cartesian
679db45
to
c9c5474
Compare
bcc3430
to
9c60804
Compare
Initial code publication
Move the source code from the internal repo, refine the structure, and add a dummy Python package.
The first commit contains the code reviewed and approved for publication by the Volvo Cars Open Source Program Office.
Most of the following changes are structural refinements or dummy configs.
A large part of implementation is in prototype state and is not a subject of review in this pr. The strategy for this debt is the following:
As one said, everything should be built top-down, except the first time 🙂