On 8 March 2016 at 16:14, Milan Bouchet-Valat <[email protected]> wrote:
> > julia> Array{Int}(1)
> > 1-element Array{Int64,1}:
> > 140180935446712
> This is a one-element array with uninitialized memory. There's a
> discussion going on about whether to change this to return 0 or not:
> https://github.com/JuliaLang/julia/issues/9147
>
>
Ok... So I was thinking that there could be a function called array() or
Array() that does what collect() does right now. Just for the consistency.
> > Can you tell me about the plans to move to a single string type? Does
> > that mean that the proliferation of string types (AbstractString,
> > ASCIIString, UTF8String, etc) is going to end?
> See https://github.com/JuliaLang/julia/pull/14383
>
> There should only remain String (concrete) and AbstractString in Base.
> Packages will still be able to provide custom string types.
>
That is really good news. Then it would make sense to un-deprecate
Base.String and make it do something similar to what `string()` does today.
Cheers,
Daniel.
