-
Notifications
You must be signed in to change notification settings - Fork 60
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
Parsing Julia types from c++ types in yaml description #310
Conversation
…ASoft#299) * Handle cases where LD_LIBRARY_PATH is not set * Add protected constructors to CollectionBase
* Split options into several lines for cleaner diffs * Remove no longer available options for disable * Remove no longer available options * Fix pylint warnings (mostly f-string usage)
…collection has been moved (AIDASoft#286)
Flagged by coverity
* Make SIO collection id writing independent of EventStore * Remove the CollectionID table member Store the necessary information in members that are written to decouple this block more from the details of podio * Move the build version into a separate block
… cmake macro (AIDASoft#282) Co-authored-by: Valentin Volkl <[email protected]>
* hotfix for AIDASoft#290 make sure that there are no unknown symbols in podioDict
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @soumilbaldota,
thanks for adding this. This looks pretty good already. I have a few comments inline that would potentially make the parse_julia_type
function a bit easier to read as it should hopefully remove a few if
s.
The function looks good to me (apart from the nitpicky comment about the f-string). I see that you have essentially duplicated the file structure of the c++ templates for the julia templates. I am not sure if we need all of those in the end, so I would suggest to add the julia template files as we need them. pylint seems to be complaining about some formatting: https://github.com/AIDASoft/podio/runs/7131646471?check_suite_focus=true#step:4:280 |
Could you also add some checks to the MemberParser tests, to make sure that the parsed julia types are as expected? These tests are here podio/python/test_MemberParser.py Line 15 in 9d078f8
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks good to me. Is there anything still missing from your side, that you would like to still have in this PR?
Otherwise I would suggest to have the next step in a new PR.
Hi @tmadlener , |
…473) * Parsing Julia types from c++ types in yaml description (#310) * Julia preprocessing (#311) * adding pre-processing/"include" logic for julia * Add templates for Julia code * Add Julia unittests to test suite (#322) * grouping code into modules * add documentation for Julia code generation (#329) * Added abstract types in default parameters and '-l' language argument * Added --upstream-edm code generation support * Created _sort_components_and_datatypes function to perform topological sort * Added abstract support for builtin Vector Members * Added conditional check for StaticArrays * Suggested Changes * Added ENABLE_JULIA toggle --------- Co-authored-by: soumilbaldota <[email protected]> Co-authored-by: Thomas Madlener <[email protected]>
BEGINRELEASENOTES
ENDRELEASENOTES