Marc-André Lafortune

I haven't had the time to check the API for tracepoint. Can you `raise NotImplementedError` for the cases that are not handled?

I've introduced actual automated tests for backports. Could you fix https://travis-ci.org/marcandre/backports/jobs/5226693 ? Also, could you copy MRI's tests and adapt them? There might be some `{new_syntax: 1}` to change to...

Cool. The test will fail if including your file issues warnings in verbose mode. The indentation is screwed up because you have tabs in your file... MRI tests are in...

Mmm, looks like I completely forgot about this. So as far as you're concerned, this is as complete as can be, then?

BTW, I've done `caller_locations`, just have not pushed it yet.

Ok, I'll have to review the code, squash the commits, and figure out why the build does not pass...

- Use `prepend` or keep using `alias_method_chain`?

I wouldn't mind having a nicer API too. E.g.: ``` Backports.update :to_h, :transform_values, up_to: 2.7 ``` That would still be susceptible to forward incompatiblities if the `up_to` argument is optional....

I've started on 2.0 (Enumerator::Lazy). I can accept patches now. They will need to be required explicitly (`require 'backports/2.0.0'`) until Ruby 2.0.0 final is released.

Thanks for the PR. The `debugging` feature feels like a definite no-no, and the fact that the events (e.g. `swiperight`) are replace by others (e.g. `swipefromleft`) is completely out of...