Skip to content
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

Support positional/ordered and nominal/unordered data objects/records #43

Open
amis92 opened this issue Jul 5, 2018 · 2 comments
Open
Labels
API design Generated API design discussions enhancement
Milestone

Comments

@amis92
Copy link
Owner

amis92 commented Jul 5, 2018

Positional records have public "primary" constructor and the order of their properties matters. They support all features but are not extensible while keeping backwards compatibility.

Nominal records have no accessible constructor, have to be built using builder or factory methods, order of their properties does not matter, and they can be extended with additional members while keeping binary compatibility with older versions.

@amis92 amis92 added this to the Future milestone Jul 26, 2019
@amis92
Copy link
Owner Author

amis92 commented Jul 26, 2019

@amis92
Copy link
Owner Author

amis92 commented Jul 26, 2019

Maybe we can build something similar, or would hiding the constructor be enough?

@amis92 amis92 added the API design Generated API design discussions label Aug 6, 2019
@amis92 amis92 changed the title Separate unordered-data classes generation Support positional/ordered and nominal/unordered data objects/records Aug 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API design Generated API design discussions enhancement
Projects
None yet
Development

No branches or pull requests

1 participant