/ doc / tocNamespace / ARCCore / PValue<T>

PValue<T>

Edit keys at this level only

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

__TOCDet/Assembly = ARCCore
__TOCDet/Description = Single value storage.0x000D0x000A0x000D0x000AUsed for storing single property values (without metadata), like customer's 'FirstName' and 'LastName'.0x000D0x000A0x000D0x000AThe most memory-efficient 'property'-object to use, when only the actual value of a property is needed.0x000D0x000A(unable to store any sub-properties or metadata).0x000D0x000ABut see also -PExact- which stores values directly, and uses this class -PValue- only for packing and unpacking the values.0x000D0x000A0x000D0x000AImmutable (assuming generic type is also immutable).0x000D0x000A0x000D0x000ATypically used for storing properties like 'Customer.FirstName', 'Product.Price' and so on.0x000D0x000A0x000D0x000AThis class supports duck-typing, especially in -TryGetV- which can return a basic value type like int, long, double, DateTime, TimeSpan, enum based on a string value, or even convert between values, like returning a double if the original -Value- is an int and so on.0x000D0x000AIt is still however recommended to have a strongly typed schema, that is, using -PKTypeAttribute- in order to specify the original type of a value.0x000D0x000ASee also -ConvertObjectToString-.0x000D0x000A0x000D0x000AWhen storing of metadata is desired, a more complicated approach is used. See -Value- for a more detailed explanation about this0x000D0x000AUsing this class should give an overhead per object of 24 bytes (16 for object header, 8 for -Value-), in addition to the space needed for the actual object (of type T) stored. Note, when calculating space needed for the actual object (of type T) you must remember to include boxing-overhead for value types.0x000D0x000ASee also -MemoryConsumption-.0x000D0x000A0x000D0x000ATODO: Consider creating a PValueVal-class for storing value types. This should get rid of boxing...?0x000D0x000ATODO: (However, no practical use-case has been seen as of Jul 2020 because of -PExact- TODO: which stores objects directly within an Object0x005B0x005D, that is, not using -PValue- at all.)0x000D0x000A0x000D0x000ASee also -MemoryConsumption-.
__TOCDet/DocFragType = Class
__TOCDet/Name = PValue0x003CT0x003E
__TOCDet/Namespace = ARCCore
__TOCDet/Type = PValue0x003CT0x003E
__TOCDet/Attribute/AssemblyName = ARCCore
__TOCDet/Attribute/ClassNamespace = ARCCore
__TOCDet/Attribute/ClassType = PValue0x003CT0x003E
__TOCDet/Attribute/Description = Single value storage.0x000D0x000A0x000D0x000AUsed for storing single property values (without metadata), like customer's 'FirstName' and 'LastName'.0x000D0x000A0x000D0x000AThe most memory-efficient 'property'-object to use, when only the actual value of a property is needed.0x000D0x000A(unable to store any sub-properties or metadata).0x000D0x000ABut see also -PExact- which stores values directly, and uses this class -PValue- only for packing and unpacking the values.0x000D0x000A0x000D0x000AImmutable (assuming generic type is also immutable).0x000D0x000A0x000D0x000ATypically used for storing properties like 'Customer.FirstName', 'Product.Price' and so on.0x000D0x000A0x000D0x000AThis class supports duck-typing, especially in -TryGetV- which can return a basic value type like int, long, double, DateTime, TimeSpan, enum based on a string value, or even convert between values, like returning a double if the original -Value- is an int and so on.0x000D0x000AIt is still however recommended to have a strongly typed schema, that is, using -PKTypeAttribute- in order to specify the original type of a value.0x000D0x000ASee also -ConvertObjectToString-.0x000D0x000A0x000D0x000AWhen storing of metadata is desired, a more complicated approach is used. See -Value- for a more detailed explanation about this0x000D0x000AUsing this class should give an overhead per object of 24 bytes (16 for object header, 8 for -Value-), in addition to the space needed for the actual object (of type T) stored. Note, when calculating space needed for the actual object (of type T) you must remember to include boxing-overhead for value types.0x000D0x000ASee also -MemoryConsumption-.0x000D0x000A0x000D0x000ATODO: Consider creating a PValueVal-class for storing value types. This should get rid of boxing...?0x000D0x000ATODO: (However, no practical use-case has been seen as of Jul 2020 because of -PExact- TODO: which stores objects directly within an Object0x005B0x005D, that is, not using -PValue- at all.)0x000D0x000A0x000D0x000ASee also -MemoryConsumption-.
__TOCDet/Attribute/Interfaces = IEquatable0xoooo003CPValue0xoooo003CT0xoooo003E0xoooo003E0x003BIP0x003BIEnumerable0xoooo003CIKIP0xoooo003E0x003BIEnumerable
__TOCDet/Attribute/InterfacesDirectlyImplemented = IEquatable0xoooo003CPValue0xoooo003CT0xoooo003E0xoooo003E0x003BIP0x003BIEnumerable0xoooo003CIKIP0xoooo003E0x003BIEnumerable

Edit single sub keys only: __TOCDet

Generated 2025-10-11 03:46:35.836 UTC