Translations:Value type/8/en: Difference between revisions

From Resonite Wiki
Importing a new version from external source
 
Importing a new version from external source
 
Line 1: Line 1:
In ProtoFlux, in short, if a type can be classified as an [https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/builtin-types/unmanaged-types unmanaged type in C#], it is recognized as a value type. Otherwise, it is an [[Object Type]]. This makes ProtoFlux's type categorization a direct interface to C#'s type categorization.
In ProtoFlux, in short, if a type can be used within the [https://learn.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/constraints-on-type-parameters#unmanaged-constraint unmanaged type constraint in C#], it is recognized as a value type. Otherwise, it is an [[object type]]. This makes ProtoFlux's type categorization a direct interface to C#'s type categorization.

Latest revision as of 10:40, 25 October 2025

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Value type)
In ProtoFlux, in short, if a type can be used within the [https://learn.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/constraints-on-type-parameters#unmanaged-constraint unmanaged type constraint in C#], it is recognized as a value type. Otherwise, it is an [[object type]]. This makes ProtoFlux's type categorization a direct interface to C#'s type categorization.

In ProtoFlux, in short, if a type can be used within the unmanaged type constraint in C#, it is recognized as a value type. Otherwise, it is an object type. This makes ProtoFlux's type categorization a direct interface to C#'s type categorization.