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.

Sign up for GitHub

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

Jump to bottom

Consider singleton implementation for item objects, i.e. one object per id. #129

Open
vijayiyer05 opened this issue Jul 22, 2021 · 0 comments
Open

Consider singleton implementation for item objects, i.e. one object per id. #129

vijayiyer05 opened this issue Jul 22, 2021 · 0 comments

Comments

@vijayiyer05
Copy link
Collaborator

vijayiyer05 commented Jul 22, 2021 •
edited
Loading

This might be desirable to prevent duplicate object construction.

One challenge would be to handle the array construction case, e.g. if a subsequent call to constructor sought to make an array including an already-constructed scalar.
@vijayiyer05 vijayiyer05 mentioned this issue Jul 22, 2021
Closed
1 task
@vijayiyer05 vijayiyer05 changed the title Consider viability of a singleton implementation for item objects, i.e. one object per id. Would need to consider the array construction case, e.g. if a subsequent call to constructor sought to make an array including an already-constructed scalar. Consider viability of a singleton implementation for item objects, i.e. one object per id. Jul 22, 2021
@vijayiyer05 vijayiyer05 changed the title Consider viability of a singleton implementation for item objects, i.e. one object per id. Consider singleton implementation for item objects, i.e. one object per id. Jul 22, 2021
@vijayiyer05 vijayiyer05 mentioned this issue Aug 7, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vijayiyer05