We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
No description provided.
The text was updated successfully, but these errors were encountered:
A very aggressive idea on this: Could we decouple types and storage / representation further?
if there's a
class Point(var x, var y)
it says it provides x, y fields following the ownership model.
x
y
A boxed version of "Point" provides this, with a heap representation, where these two fields can be accessed from the heap.
An array version of "Point" provides this, where these two fields corresponds to continuous memory.
A json version of "Point" provides this, with a json representation, where these fields are represented within json representation too.
Sorry, something went wrong.
Neat idea.
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: