Unify type encoding for similar types#4331
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"? |
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. |
|
What the status of this PR? (Besides the merge issues, the last comment was in November 2024) |
|
The example from paper will now look like this. (not all changes are from this upgrade, only the type info changes) |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4331 +/- ##
==========================================
- Coverage 84.88% 84.87% -0.01%
==========================================
Files 683 683
Lines 91859 91883 +24
==========================================
+ Hits 77976 77990 +14
- Misses 13883 13893 +10
🚀 New features to boost your workflow:
|
663602e to
9f4f549
Compare
benlorenz
left a comment
There was a problem hiding this comment.
A few small remarks, otherwise this should be good to merge.
These changes allow for a many to one serialization.
The use case is to have a single "name" for types with the same encoding.
The Oscar type is now stored using the "_instance" keyword, when there isn't a bijection between the type
and the type "name"