Bug 216761 – Need a better name for Gigacage::Config, WTF::Config, and JSC::Config.

• Status: ASSIGNED
• Component: JavaScriptCore

[Mark Lam]

Both Darin and Sam Weinig has asked me about the naming of these Config records before.  Everyone agrees that the current name is not great.  What we don't have yet is a better name we can use.

The Config records have the following properties:
1. They hold values that are mutable at initialization time.
2. These values are frozen at some point before any scripts are executed, and are read-only after the point of freezing.

I had considered ConstData or ReadOnlyData, but those are inaccurate with respect to property (1).  They are currently named Config (short for configuration) because they hold values they configures the behavior of the system in one way or another.  This is not a requirement for what can be placed in these records though.  The only requirement is that the values in them can be permanently frozen before the system starts executing scripts.

Some possible option for an alternative name might be ReadOnlyLateData or LateReadOnlyData. These are still not ideal.

I kind of prefer something like IcedData as in data that has been frozen, although "ice" is not a commonly used term in coding circles.  IcedData is short and strongly hints at the properties of the data.  Any thoughts?

[Mark Lam]

Keith M. suggested FrozenData instead of IcedData because it's more straightforward.  After thinking about it some more, I think FrozenData is the best suggestion we have so far.  Unlike ConstData / ReadOnlyData, "Frozen" implies there was a freezing action at some point, which is accurate.

Unless we get better suggestions, I'll do a rename of Config to FrozenData later.

[Radar WebKit Bug Importer]

<rdar://problem/69680480>