replace complex spec values with spec records

[michaelficarra]

The spec currently refers to the components of execution contexts in a couple different ways. They are referred to in at least the following ways:

• "the ComponentName of variableName"
• "the ComponentName component of variableName"
• "variableName's ComponentName"
• "variableName's ComponentName component" (only one use, I will PR it away)

We should choose one and normalise the format. I'm also not sure why execution contexts are not just spec records like basically everything else.

[jmdyck]

I'm also not sure why execution contexts are not just spec records like basically everything else.

About the only reason I can think of is that the code evaluation state component is implementation-dependent, which raises the question of what you would put for its value in a record 'literal'. But that can be handled one way or another.

I think modeling Execution Context as a Record would be an improvement.

[michaelficarra]

We should convert References to spec records as well.

edit: See #2085.

[michaelficarra]

A State in the Pattern Semantics section contains an ordered pair. We should use spec records there as well.

[ExE-Boss]

See also:

• Atomics and memory model specification questions/issues #800
• Editorial: Describe WaiterList using Records #2240