Merge pull request #7047 from tanmaykm/tanmaykm

1d set/getindex for abstract sparse
@timed: also include GC time as third returned value.
REPL history: seek to end before writing; print with sinlge call.

Even better would be if we could write lock the file before doing
this and then release the lock after, to guarantee that two REPL
processes can't write to it at the same time, but this is better.

Hopefully fix #7156.
mention angle function in manual (closes #7149)
Fix #6275

The approach is as follows. On MCJIT with LLVM trunk we get proper line numbers.
On 3.3 we get proper line numbers on Linux (and probably Windows), but on Mac,
you have to use a patched version of LLVM. If you don't use the patched version
of LLVM you'll still get the function names but no line numbers.
Nasty LLVM 3.3 support
Linux support
add a news entry about recent changes to reduce.jl & reducedim.jl
Add FAQ section on DomainErrors and type-stability

This has come up many times on the user list; time for a FAQ.
Update mailmap
Merge branch 'master' of github.com:JuliaLang/julia
Fix trailing newlines in prompt corrupt history

.julia_history stores the prompt text with leading tab indentation, and the
REPL expects all prompt lines to start with a `\t`. Previously, these tabs were
inserted when writing to the history file by substituting line starts (r"^"ms)
with a tab character. However, final newlines are not considered line starts,
so they were entered into the history file without the tab, which corrupts the
file.

This fixes that, by prefixing the prompt with a `\t` and then replacing all
newlines with `\n\t`.
Parametrize Triangular on matrix type
Merge pull request #7164 from mbauman/repl-trailing-newlines

Trailing newlines in prompt corrupt the history file
REPL history: ignore blank lines except in the history entry itself.

Blank lines before, during, or after the metadata block are ignored.
REPL history: rstrip all history entries instead of b5fc8c84bc.

My main issue with the replace '\n' approach is that some people
have crazy systems where '\r\n' or even '\r' is the standard line
ending. Even if we don't produce anything but '\n', people might
open history files in their editors which could save the files
with different line endings. Instead, this just strips trailing
whitespace from history entires, ensuring that trailing newlines
cannot be produced. Of course, I also modified the history parser
so that it ignores newlines, so even if these were produced, it
wouldn't be an issue anymore.
Merge pull request #7155 from ArchRobison/adr/haswell

Enable AVX for  Intel 4th-Generation Core processor ("Haswell") .
REPL history: print the timestamp before the mode.
cosmetic changes to base/statistics.jl (prepare for further refactoring)
fix inference's argument checking of arrayset. fixes #7130