Andy Ferris

I'm wondering if `SA` is would be confusing for people who aren't direct *StaticArrays.jl* users. We are used by a lot of downstream packages and general Julia users may receive...

> I'm a bit surprised that SVector{2}(Any[1, 2]) doesn't work Oh, so am I! Even `convert` is broken, and neither match `Base`. ```julia julia> SVector{2}(Any[1,2]) 2-element SVector{2, Int64} with indices...

In my opinion, it's important to mimic `Base` as closely as possible, to help people write generic code and avoid surprises when using StaticArrays. While this is more important for...

The reason in Base that it is safe to e.g. have an operation on two `Float16`s return another `Float16` is that these types have `NaN16`, `Inf16` and `-Inf16`. For `UInt8`...

Good points. It's definitely a tricky one. I note that some of these things really need fixing, outside of this package, like initializing accumulators, but these are also very tricky...

I've been thinking about naming conventions in Displaz, and I'm begining to believe the solution might be in not exporting any commands at all, and choosing simple names, like this:...

Regarding type stability problems with the keywords - is it better to propagate the `by` keyword or the `By` type (and friends) to other functions throughout `Base`? Will keyword argument...

I just came across the `==` problem. > This comes from the fact that Nullable(1) == 1 At first glance that seems _insane_ to me. Don't we have different things...

Well, we have `1.0 == 1` as `true` and many many other examples. `==` is meant to be the "handwavey", and "its close enough in _meaning_" (not implementation) type of...

Yes, sorry for being unclear, but I did mean the latter. While I _do_ think #85 is a good idea (and I do understand the difficulties and have read a...