-
Notifications
You must be signed in to change notification settings - Fork 31
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
std::nullptr_t
should be an acceptable ctor for all Scoped
types.
#274
Milestone
Comments
copybara-service bot
pushed a commit
that referenced
this issue
Mar 21, 2024
…in the API). In rare instances classes may want to have uninitialized members that reside on the stack. Previously, the base declaration will call the constructor with no arguments, but this API provides for declaring members with "LocalObject<kClass> obj{nullptr};" syntax. #274 PiperOrigin-RevId: 617944956
copybara-service bot
pushed a commit
that referenced
this issue
Mar 21, 2024
…in the API). In rare instances classes may want to have uninitialized members that reside on the stack. Previously, the base declaration will call the constructor with no arguments, but this API provides for declaring members with "LocalObject<kClass> obj{nullptr};" syntax. #274 PiperOrigin-RevId: 617944956
copybara-service bot
pushed a commit
that referenced
this issue
Mar 21, 2024
…in the API). In rare instances classes may want to have uninitialized members that reside on the stack. Previously, the base declaration will call the constructor with no arguments, but this API provides for declaring members with "LocalObject<kClass> obj{nullptr};" syntax. #274 PiperOrigin-RevId: 617944956
copybara-service bot
pushed a commit
that referenced
this issue
Mar 21, 2024
…in the API). In rare instances classes may want to have uninitialized members that reside on the stack. Previously, the base declaration will call the constructor with no arguments, but this API provides for declaring members with "LocalObject<kClass> obj{nullptr};" syntax. #274 PiperOrigin-RevId: 617944956
copybara-service bot
pushed a commit
that referenced
this issue
Mar 21, 2024
…in the API). In rare instances classes may want to have uninitialized members that reside on the stack. Previously, the base declaration will call the constructor with no arguments, but this API provides for declaring members with "LocalObject<kClass> obj{nullptr};" syntax. #274 PiperOrigin-RevId: 617944956
copybara-service bot
pushed a commit
that referenced
this issue
Mar 21, 2024
…in the API). In rare instances classes may want to have uninitialized members that reside on the stack. Previously, the base declaration will call the constructor with no arguments, but this API provides for declaring members with "LocalObject<kClass> obj{nullptr};" syntax. #274 PiperOrigin-RevId: 617944956
copybara-service bot
pushed a commit
that referenced
this issue
Mar 21, 2024
…in the API). In rare instances classes may want to have uninitialized members that reside on the stack. Previously, the base declaration will call the constructor with no arguments, but this API provides for declaring members with "LocalObject<kClass> obj{nullptr};" syntax. #274 PiperOrigin-RevId: 617944956
copybara-service bot
pushed a commit
that referenced
this issue
Mar 22, 2024
…in the API). In rare instances classes may want to have uninitialized members that reside on the stack. Previously, the base declaration will call the constructor with no arguments, but this API provides for declaring members with "LocalObject<kClass> obj{nullptr};" syntax. #274 PiperOrigin-RevId: 618004432
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All types should support being initialized with
nullptr
but this appears to be inconsistent.This behaviour is still supported through explicitly passing the tag type (e.g.
jobject{nullptr}
etc). But this should be a consolidated implementation.The text was updated successfully, but these errors were encountered: