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
Thrust code snippets under the reference page of our algorithms are poor in two way.
Although we need to keep the concise we also need to make them more complete. Per the cppreference style of examples, we need clear distinction between input and output in the text. Encourage the use of thrust::device_vector instead of custom allocated arrays. Showcase both generic cases and edge cases.
Extract them to literalincludes to make sure they are full compilable scripts that can be cut pasted into main(). It's very discouraging for a new user when that's not the case. This should also resolve:
Thrust code snippets under the reference page of our algorithms are poor in two way.
Although we need to keep the concise we also need to make them more complete. Per the cppreference style of examples, we need clear distinction between input and output in the text. Encourage the use of
thrust::device_vector
instead of custom allocated arrays. Showcase both generic cases and edge cases.Extract them to literalincludes to make sure they are full compilable scripts that can be cut pasted into
main()
. It's very discouraging for a new user when that's not the case. This should also resolve:thrust::partition_copy
docs are wrong #2792thrust::stable_sort
docs are wrong #2747copy_n
docs formatting bug #2748.The text was updated successfully, but these errors were encountered: