Closed Bug 1185390 Opened 10 years ago Closed 9 years ago

Remove proto argument from NewObjectWithClassProto

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: evilpies, Assigned: evilpies)

References

Details

We already have NewObjectWithGivenProto, so you should always get the ClassProto instead of calling out from NewObjectWithClassProtoCommon when somebody passes a proto.
Assignee: nobody → evilpies
This seems like a lost cause and maybe this isn't too bad. Duplicating this logic in all the callers is probably worse.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.