Closed Bug 1645327 Opened 5 years ago Closed 5 years ago

Make naming of TestingFunctions feature predicates more uniform

Categories

(Core :: JavaScript: WebAssembly, enhancement, P3)

Product:
Core
Component:
JavaScript: WebAssembly
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: lth, Unassigned)

Details

We have wasmFeatureSupported, wasmFeatureSupport, and wasmFeatureEnabled, and this is maddening. Surely we need only one of these for almost every case. See the patch of bug 1643653 for a related discussion of a corner case. The discussion is to change the names of all of these to be wasmFeatureAvailable uniformly, since whether something is "supported" or "enabled" is almost always beside the point - we care about whether it is available, a function of being supported, enabled, and not being blocked by other features or by compiler selection.

Assignee: lhansen → nobody
Status: ASSIGNED → NEW
Assignee: nobody → lhansen
Status: NEW → ASSIGNED
Assignee: lhansen → nobody
Status: ASSIGNED → NEW

I believe this was improved as part of bug 1664361.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.