Add documentation to note that compiler internal constructs should not be expected to get full error checking about slang HOT 7 CLOSED

We are deprecating __target_intrinsic for functions and we recommend all future interop code to be written in the form of __target_switch and __intrinsic_asm. As you noticed, __require_prelude and __intrinsic_asm does not work when __target_intrinsic is present.

from slang.

Tentatively assigned labels-- Yong, please advise if this is a "we should add a warning" or something else.

from slang.

__target_intrinsic is still considered as compiler internal construct and we probably won't plan to add too much comprehensive checking logic around it. We may want to expose something different to the user that will undergo more checking. My suggestion is to close this issue because we don't want to invest too much checking in internal constructs for performance and implementation simplicity considerations.

from slang.

That sounds reasonable -- do we need to add any documentation?

from slang.

We can add a line in https://github.com/shader-slang/slang/edit/master/docs/user-guide/a1-04-interop.md to say that the constructs are still considered compiler internal and users should expect less complete checking around them.

from slang.

Thanks! Updated title, lowered priority, moved to backlog.

from slang.

We are deprecating __target_intrinsic for functions

Is there a list of deprecated things? I thought as it was part of the User Guide I was supposed to use it.

we recommend all future interop code to be written in the form of __target_switch and __intrinsic_asm

I can also use this.

Generally, what is the suggested way to extend on already existing types that are already in place for spir-v or hlsl but not for C++? I tried to write C++ bindings for the RayQuery struct. Currently it works by redefining the type in case I am compiling for C++, as inheriting from the already existing RayQuery struct is forbidden (sealed type). But I have the feeling that this is not the right way to go as this approach relies on preprocessor logic instead of actual language features. Can you give me some guidance on this? Is there documentation or examples somewhere that I missed?

from slang.