Closed Bug 1173513 Opened 5 years ago Closed 5 years ago

Point to SavedFrame.md docs from JSAPI comments

Categories

(Core :: JavaScript Engine, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla41
Tracking Status
firefox41 --- fixed

People

(Reporter: fitzgen, Assigned: fitzgen)

Details

Attachments

(1 file, 1 obsolete file)

No description provided.
Assignee: nobody → nfitzgerald
Status: NEW → ASSIGNED
The pointer should be from the jsapi bits for async stacks/causes (also?), no?
(In reply to Not doing reviews right now from comment #2)
> The pointer should be from the jsapi bits for async stacks/causes (also?),
> no?

Do you want to repeat the "See also ..." for each method? I personally think that's a bit much, but you are an API customer and I am not, so I defer to you.
Well.  So I was reading the docs for AutoSetAsyncStackForNewCalls when I couldn't make sense of asyncCause.  That's about 1000 lines above the line you're adding.  What are my chances of starting at AutoSetAsyncStackForNewCalls and discovering that I should read SavedFrame.md for documentation on asyncCause?
https://hg.mozilla.org/mozilla-central/rev/680292fc9f89
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
You need to log in before you can comment on or make changes to this bug.