Allow creating another constructor (without validation) with new_empty_object()
#581
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #522
Allows us to create a constructor separately from the S7 class definition.
The expected use is to create an empty (invalid) object when the package is loaded, and then the second constructor sets properties on it and creates a valid object.
It is also possible for the first constructor of the S7 class to depend on the second constructor.
The second constructor may completely bypass the validation step, making object creation much faster, which I think is very important in packages like polars where we create objects multiple times.
(It is entirely up to the package developer to ensure that the second constructor creates a valid object without validation.)
Created on 2025-11-26 with reprex v2.1.1