You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it could prevent confusion if c++ binding types could be written with "cxx::" module perfix in the extern blocks.
For example, in the Blobstore example we have
If one writes the return type of new_blobstore_client() with cxx::UniquePtr<BlobstoreClient> instead, there is compilation error "unsupported type". Users may think cxx::UniquePtr to be the correct way write the type, because cxx namespace has not been opened up with use cxx::*;. The error message may misslead newcomers into thinking that there is something in their current interface design that is not supported by cxx.
The text was updated successfully, but these errors were encountered:
I think it could prevent confusion if c++ binding types could be written with "cxx::" module perfix in the extern blocks.
For example, in the Blobstore example we have
If one writes the return type of
new_blobstore_client()
withcxx::UniquePtr<BlobstoreClient>
instead, there is compilation error "unsupported type". Users may thinkcxx::UniquePtr
to be the correct way write the type, because cxx namespace has not been opened up withuse cxx::*;
. The error message may misslead newcomers into thinking that there is something in their current interface design that is not supported by cxx.The text was updated successfully, but these errors were encountered: