[SYCL][NFC] Move KernelWrapper outside the sycl::handler

[uditagarwal97]

KernelWrapper is also used in the no-handler submission path, so moving this struct outside the handler class into the detail:: namespace. This PR also moves functions like kernel_single_task that are called by KernelWrapper outside the sycl::handler class.

[slawekptak]

I would consider removing the properties parsing from the KernelWrapper class - we could avoid passing the handler to the wrap function. Also, I feel that it might be cleaner, if the KernelWrapper is responsible just for wrapping of the kernel. I think the utility functions for property processing may still be in this header, but maybe as separate functions. Does it make sense?

[uditagarwal97]

I'll make that change in a follow up PR.

[slawekptak]

This function is now only doing the validation, right? Maybe it can be called "validateProperties" or something similar?

[uditagarwal97]

I'll be decoupling property processing from KernelWrapper in a subsequent PR, so I'll rename this method then.

[slawekptak]

This change looks great, thanks Udit!

[Copilot]

Pull Request Overview

This PR moves the KernelWrapper struct and related kernel launch functions outside the sycl::handler class into the detail:: namespace to support their use in no-handler submission paths. The refactoring creates a new kernel_launch_helper.hpp header containing the moved code while updating references throughout the codebase.

• Moved KernelWrapper and KernelWrapperSingletonFuncs from handler class to detail:: namespace
• Created new header sycl/kernel_launch_helper.hpp for kernel launch utilities
• Updated template parameter types and function calls to accommodate the new namespace structure

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.

File	Description
sycl/kernel_launch_helper.hpp	New header containing moved KernelWrapper and kernel launch functions
sycl/handler.hpp	Removed kernel wrapper code and updated references to use detail:: namespace
Test files	Updated expected error locations from handler.hpp to kernel_launch_helper.hpp
sycl_detail_core.hpp.cpp	Updated include dependency order due to header reorganization

[sarnex]

esimd test change lgtm

[aelovikov-intel]

How much do you need? Would it be reasonable to use HandlerAccess above instead?

[uditagarwal97]

If I understand your question correctly, the idea is to reuse KernelWrapper for no-handler submission path, so it would be better to keep HandlerAccess and KernelWrapper separate.