Make DecoderFactory use NotNull where possible

RESOLVED FIXED in Firefox 50

Status

()

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: seth, Assigned: seth)

Tracking

(Blocks: 1 bug)

unspecified
mozilla50
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox50 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
I'm trying to move us over to using NotNull<> where possible in ImageLib. As DecoderFactory is the location of some refactoring right now, it feels like a good time to use NotNull<> in its API.
(Assignee)

Updated

3 years ago
Blocks: 1282354
(Assignee)

Comment 1

3 years ago
Created attachment 8765329 [details] [diff] [review]
Make DecoderFactory use NotNull where possible.

Here's the patch.
Attachment #8765329 - Flags: review?(edwin)
(Assignee)

Updated

3 years ago
Blocks: 1283286

Comment 2

3 years ago
Pushed by mfowler@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/c607a8652548
Make DecoderFactory use NotNull where possible. r=edwin

Comment 3

3 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/c607a8652548
Status: NEW → RESOLVED
Last Resolved: 3 years ago
status-firefox50: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
You need to log in before you can comment on or make changes to this bug.