[SYCL] Remove cl namespace deprecation warning #6735
Conversation
According to the SYCL 2020 specification, CL/sycl.hpp should supply the cl prefix namespace for backwards compatibility, but it does not specify that the namespace is deprecated. This commit removes the deprecation message. Signed-off-by: Larsen, Steffen <steffen.larsen@intel.com>
aelovikov-intel
left a comment
aelovikov-intel
left a comment
There was a problem hiding this comment.
I wonder why the spec didn't actually deprecate it... Also, I think all the actually "deprecated" things are left for some time for "compatibility" reasons and allowing the user to update the codebase.
How is this namespace so different that the spec doesn't intend to remove it?
I am not certain what the intention was in not deprecating it, but until the spec says that it is deprecated we should not deprecate it. Many things were removed from 1.2.1 that were not deprecated before removal, so similar to how we treat those while implementing SYCL 2020, if the next version of SYCL removes the backwards-compatibility header and namespace we can deprecate it then. |
3 participants
According to the SYCL 2020 specification, CL/sycl.hpp should supply the cl prefix namespace for backwards compatibility, but it does not specify that the namespace is deprecated. This commit removes the deprecation message.