-
Notifications
You must be signed in to change notification settings - Fork 129
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
proto type for many to one type serialization #4331
base: master
Are you sure you want to change the base?
Conversation
Default type storing
Non default types have
|
Should I be irritated by these comments in the code?
What does it mean that "I can't figure out how to get sending types to strings to behave properly"? |
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.
See above.
This is mainly a todo for me, I describe this issue in the description for the pull request. It appears that I've commented in the code the places where the unexpected results are happening (see following commit) |
to location where unexpected results occur
The changes would have the following consequences on the example in the paper.
|
with the latest commit example file looks like this
|
We agreed that there should be an _instance entry every time where the many to one map is not bijective, even if suitable OSCAR defaults are in place. With this addition the PR is good for merge IMHO. |
This pull request should not neccesarily be merged.
It is just to demonstrate a possible mechanic for having a many types to one serialization
where multiple types share the same encoding.
I put it in a pull request to highlight the changes and to start to discuss if this is viable solution and
to discuss the potential pitfalls of such a mechanism.
I have an unsafe line of code that I comment on, but this should be fixable, I just couldn't figure out
why sometimes string(fpField) = "Nemo.fpField" and sometimes it is string(fpField) = "fpField"