-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Member initialisation order error. #443
Comments
Well, that's not an error - you're not required to initialize in the same order, but - sure, it's nicer to do it in order. |
Yeah, I suppose it's technically a warning. But I didn't have "warnings as errors" enabled... Anyway, thanks again! |
@j-horner-c4x : It may take a little time before 0.6.2 comes out with this integrated. For now you'll need to either use the development branch or reverse the order yourself. |
First, thanks for putting the time into making this library.
I got an error when using
cuda::memory::device::unique_ptr<T[]>
In version 0.6.1.
Swapping the initialisation order in the constructor to match the member list fixes the issue.
The text was updated successfully, but these errors were encountered: