Tony Kelman

`test/perf` is not especially useful, it very rarely gets run - BaseBenchmarks.jl is where we should add things so nanosoldier tracks them

> how did this code ever work ccall used to be oddly permissive of invalid code in parts it didn't use or call

I'd be interested to see some of the symmetric indefinite methods MINRES, SYMMLQ, MINRES-QLP (http://www.stanford.edu/group/SOL/software.html)

_partial ? you might be incurring a bit of splatting penalty with the local fallback to the base methods

splatting can have a non negligible performance cost in some situations, so ``` for op in (:A_mul_B!, :At_mul_B!, :Ac_mul_B!, :scale!) @eval begin $op(args...) = Base.$op(args...) end end ``` might not...

That was just upgrading the version we build against by default. Some API's changed and added proxy options, but we don't do anything special about setting them or threading them...

When you do, be sure to add a `REQUIRE` file with at least a minimum julia version

The test we use [on Travis for `language: julia`](https://github.com/travis-ci/travis-build/blob/0cd467fff60472c85c9e81735ddeefebd1448b0d/lib/travis/build/script/julia.rb#L68) is if the repo has a file at `src/PkgName.jl`, where `PkgName` is the repo name, minus the trailing `.jl` if present....

You don't get any benefit from package management being an independent process if most users will want to run it from inside Julia most of the time. Upgrading happens often,...

You can clone from filesystem-local repositories already, though it does make a copy.