Pointer types not correctly identified as unmanaged in IsUnmanaged method #33

In the TypeExtensions class, the IsUnmanaged method does not correctly identify pointer types as unmanaged.

Current Behavior:

• The method checks if a type is a value type. If not, it returns false, which is not accurate for pointer types.
• Pointer types are not treated as unmanaged due to the conditional checks.

Expected Behavior:

• Pointer types should be identified as unmanaged to ensure correct behavior in scenarios where unmanaged types are required.

Impact:

The NativeChunk class uses the IsUnmanaged method to validate types when creating its componentArray. Since pointer types are not correctly identified as unmanaged, this issue prevents using Unity's NativeCollection types, like NativeArray and NativeList, in Job System.

Supporting Information:

According to the official Microsoft documentation on unmanaged types:

A type is an unmanaged type if it's any of the following types:

• sbyte, byte, short, ushort, int, uint, long, ulong, nint, nuint, char, float, double, decimal, or bool
• Any enum type
• Any pointer type
• A tuple whose members are all of an unmanaged type
• Any user-defined struct type that contains fields of unmanaged types only