SkPDF: AutoTUnref<T> changes in use

SkPDF: AutoTUnref<T> changes in use

    ::detach()      -> ::release()
    ::operator T*() -> ::get()

This makes all use of AutoTUnref work the same as sk_sp.
GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1772493002

Committed: https://skia.googlesource.com/skia/+/fcad44bbb1e0384620e7b738a0f5904c940a6861

[hal.canary, 2016-03-06 17:17:57]

Description was changed from

==========
SkPDF: AutoTUnref<T> changes in use

    ::detach()      -> ::release()
    ::operator T*() -> ::get()

This makes all use of AutoTUnref work the same as sk_sp.
==========

to

==========
SkPDF: AutoTUnref<T> changes in use

    ::detach()      -> ::release()
    ::operator T*() -> ::get()

This makes all use of AutoTUnref work the same as sk_sp.
GOLD_TRYBOT_URL=
https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&is...
==========

[hal.canary, 2016-03-06 17:19:23]

halcanary@google.com changed reviewers:
+ bungeman@google.com

[hal.canary, 2016-03-06 17:19:24]

ptal

[bungeman-skia, 2016-03-06 21:43:53]

The CQ bit was checked by bungeman@google.com to run a CQ dry run

[commit-bot: I haz the power, 2016-03-06 21:43:55]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1772493002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1772493002/1

[bungeman-skia, 2016-03-06 21:48:34]

lgtm, but is there any reason not to change the type of all the affected
variables and fields to sk_sp at the same time? This would make it obvious that
this is completely done and would prevent accidental regressions. Is that
planned as a follow up?

[commit-bot: I haz the power, 2016-03-06 21:53:05]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-06 21:53:06]

Dry run: This issue passed the CQ dry run.

[hal.canary, 2016-03-06 22:45:23]

On 2016/03/06 21:48:34, bungeman1 wrote:
> lgtm, but is there any reason not to change the type of all the affected
> variables and fields to sk_sp at the same time? This would make it obvious
that
> this is completely done and would prevent accidental regressions. Is that
> planned as a follow up?

That is planned as a follow-up. This CL is the annoying one.  The next one is a
simple sed command.

[hal.canary, 2016-03-06 22:45:50]

The CQ bit was checked by halcanary@google.com

[commit-bot: I haz the power, 2016-03-06 22:45:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1772493002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1772493002/1

[commit-bot: I haz the power, 2016-03-06 22:47:13]

Description was changed from

==========
SkPDF: AutoTUnref<T> changes in use

    ::detach()      -> ::release()
    ::operator T*() -> ::get()

This makes all use of AutoTUnref work the same as sk_sp.
GOLD_TRYBOT_URL=
https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&is...
==========

to

==========
SkPDF: AutoTUnref<T> changes in use

    ::detach()      -> ::release()
    ::operator T*() -> ::get()

This makes all use of AutoTUnref work the same as sk_sp.
GOLD_TRYBOT_URL=
https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&is...

Committed:
https://skia.googlesource.com/skia/+/fcad44bbb1e0384620e7b738a0f5904c940a6861
==========

[commit-bot: I haz the power, 2016-03-06 22:47:13]

Committed patchset #1 (id:1) as
https://skia.googlesource.com/skia/+/fcad44bbb1e0384620e7b738a0f5904c940a6861