Andy Ferris

OK, that works: ``` julia> function Base.convert{T,N}(::Type{NullableArray{T,N}},in::Array{Nullable{T},N}) out = NullableArray{T,N}(Array(T,size(in)),Array(Bool,size(in))) for i = 1:length(in) (out.isnull[i] = in[i].isnull) ? nothing : out.values[i] = in[i].value end out end convert (generic function with...

OK, I had to use an outer constructor instead of `Base.convert{T,N}(::Type{NullableArray, in::Array{Nullable{T},N})` because an existing constructor took ownership, but the others are all `convert`

Sure, a convert method in Base might make sense, much like we can convert a `Float` to an `Int` (if it is close to an integer) or a `Complex` to...

In StaticArrays I played with the idea of indexing the iterator in the generator directly. The user had to specify at least the size as a type parameter, so something...

@stevengj Not sure if you saw #159? I realize there are good reasons for using FIxedSizeArrays (including backward compatibility, integration into other packages, etc), and don't want to steal thunder...

No worries. There was a suggestion to add note to the READMEs of these packages which might help with this.

> Lets get this done this week and have an announcement on the user list etc! Sounds good. :smiley: I'm currently making a few architectural changes to StaticArrays and will...

> you'll notice me filing a slew of issues I look forward to it! :smile:

How would you handle this in the general case? Users would manually define how their types promote? Is there something like `promote_rule` to give guidance to `promote()`? Or a three-argument...

PS - this is another issue that I believe wouldn't exist if FixedSizeArrays inherited from AbstractArray...