Add libunwind patch from Pyston
Fix searchsorted for Ranges
Export Reverse in Base.Order
More robust solution for unused control characters

This is a better fix for #6682 - all control characters are now set to be ignored in the escape_defaults keymap. I had previously missed a few (e.g., `^]`, `^-`, `^\`) in both the search and default keymaps. This should fully prevent control characters from getting inserted by typing at the REPL (although they can still get inserted via paste).
beginswith, endswith accept Chars
Merge pull request #6780 from wsliang/reverse

Export Reverse in Base.Order
Merge pull request #6783 from mbauman/more-unused-bindings

More robust solution for unused control characters
fix #6784
fix codegen bug in static_void_instance on Type{()}
faster copy() for ObjectIdDict
avoid duplicate entries in linfo->tfunc (type inference efficiency issue)
Merge pull request #6776 from wsliang/searchsorted

Fix searchsorted for Ranges
more efficient setindex for sparsematrix
replaced splice! with deleteat!
Update C/Fortran microbenchmarks to new dSFMT path
Relax type restriction on isnan/isinf/isfinite of arrays
Merge pull request #6792 from JuliaLang/sjk/isnan

Relax type restriction on isnan/isinf/isfinite of arrays
Expand macro documentation

These changes are based somewhat on the [discussion on the julia-users list](https://groups.google.com/d/msg/julia-users/YTZM3Biy-rM/m0orpSjQ8RIJ) and somewhat on my own stumbling points as I was learning how macros worked.

Here's the motivation behind these changes:

* Stress that macros *return* an expression to be evaluated, and hopefully make it look like they're less magical to newcomers. Make `return` explicit in the examples, so it looks less like textual substitution and more like a mapping from exprs to an expr.
* Provide an example where the macro is more than just return an expression. The changes to `@assert` since the original documentation was written make this very natural without needing to contrive another example.
* Use function such as `macroexpand` and `dump` in the examples to help make things more concrete and give users tools to play with.
* Make the hygiene section introduction a bit more clear, with an emphasis that the only thing it needs to worry about is the returned expression.

I think this should help folks 'get' macros a bit quicker. I hope.
fix #6793
Fix PriorityQueue(ks, vs) constructor