You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've not fully explored this but it would appear that the C++ implementation will import Integer Types regardless of Type Size and then only throw an exception about an unsupported Type Size in the Fragment Builder. See:
This presumably means that if Integer Types with unsupported Type Size values exist in the Types Register then the Reg-XML dictionaries produced by the two implementations will be different. This is presumably undesirable (although I don't know if other differences already exist).
I've not fully explored this but it would appear that the C++ implementation will import Integer Types regardless of Type Size and then only throw an exception about an unsupported Type Size in the Fragment Builder. See:
This presumably means that if Integer Types with unsupported Type Size values exist in the Types Register then the Reg-XML dictionaries produced by the two implementations will be different. This is presumably undesirable (although I don't know if other differences already exist).
This arises from #146
The text was updated successfully, but these errors were encountered: