Removed out-of-date doxygen comment

src/cuda/api/stream.hpp

@@ -481,7 +481,7 @@ class stream_t {
 		{
 			// Is it necessary to set the device? I wonder.
 			CAW_SET_SCOPE_CONTEXT(associated_stream.context_handle_);
-			memory::device::async::detail_::set(start, byte_value, num_bytes, associated_stream.handle_);
+			memory::device::detail_::set(start, byte_value, num_bytes, associated_stream.handle_);
 		}
 
 		/// @copydoc memset(void *, int, size_t) const
@@ -504,7 +504,7 @@ class stream_t {
 		void memzero(void *start, size_t num_bytes) const
 		{
 			CAW_SET_SCOPE_CONTEXT(associated_stream.context_handle_);
-			memory::device::async::detail_::zero(start, num_bytes, associated_stream.handle_);
+			memory::device::detail_::zero(start, num_bytes, associated_stream.handle_);
 		}
 
 		/**
@@ -1053,19 +1053,6 @@ inline CUresult write_value<uint64_t>(CUstream stream_handle, CUdeviceptr addres
 	return cuStreamWriteValue64(stream_handle, address, value, flags);
 }
 
-/**
- * A function used internally by this class as the host function to call directly; see
- * @ref enqueue_t::host_function_call - but only with CUDA version 10.0 and later.
- *
- * @param stream_handle the ID of the stream for which a host function call was triggered - this
- * will be passed by the CUDA runtime
- * @param stream_wrapper_members_and_invokable a tuple, containing the information necessary to
- * recreate the wrapper with which the callback is associated, without any additional CUDA API calls -
- * plus the invokable which was passed to @ref enqueue_t::host_function_call, and which the programmer
- * actually wants to be called.
- *
- * @note instances of this template are of type {@ref callback_t}.
- */
 template <typename Function>
 void enqueue_function_call(const stream_t& stream, Function function, void* argument)
 {