In the GCC compiler, taking this data type as the argument of a nested function leads to the construction of a “trampoline”. The “tombstone” and “lock-and-key” approaches are used to avoid runtime errors with this data type. “Low-fat” examples of this data type can incorporate bounds checking. Objects of this type are replaced during deserialization in deswizzling. It’s not related to sampling, but two of these data types contain the same information in (*) aliasing. A seg fault can occur when trying to read from a “dangling” object of this type that has already been deallocated. In (10[1])C, placing an ampersand in front of a variable argument turns it into this data type, which can later be dereferenced by using an asterisk. For 10 points, name this data type that references a location in memory. ■END■