Tanner Gooding

> there are exactly no more details at https://github.com/dotnet/clangsharp From the main README: ``` A nuget package for the project is provided here: https://www.nuget.org/packages/clangsharp. A .NET tool for the P/Invoke...

> is this meant to be this way? Yes, because Clang makes breaking changes every release and it must bind against an exact version. A lot of more fundamental issues...

@3xau1o it's a general issue with nuget tools not supporting "per RID" setups and therefore no way to differentiate between what should be used for Windows vs Linux vs MacOS

This should be resolved with `20.1.2.2+` which requires .NET 10, but uses the new RID specific tool package support.

A small repro or more context so that the root issue can be resolved would be beneficial. Contributions are also welcome

This was likely fixed by https://github.com/dotnet/ClangSharp/pull/587 and https://github.com/dotnet/ClangSharp/pull/628 Closing for now due to lack a of repro and no response

> does fix this issue but its very hacky and the maintainer should really get on top of what is happening here. Looks like the issue is that the resolution...

This was resolved and should be handled in the latest tool versions.

`IsSugared` is just calling `Ty->isSugared()`: https://github.com/dotnet/ClangSharp/blob/f0501f7370c01064676f3e8100c4fe76dc3a7c62/sources/libClangSharp/ClangSharp.cpp#L5235-L5247 You'll note that `UnqualifiedDesugaredType` (https://source.clangsharp.dev/#ClangSharp/Types/Type.cs,2de64541a028759e) is itself just matching the behavior of `Type::getUnqalifiedDesugaredType`: https://clang.llvm.org/doxygen/Type_8cpp_source.html#l00605 In general ClangSharp tends to just mirror what Clang does...

Can you provide some more details about the options you're passing into ClangSharp, the version you're using, and possibly a minimal repro? ClangSharp simply passes the files down to Clang....