On Friday, July 8, 2016 6:43:36 PM CDT Daniel Carrera wrote:
> For that matter, will there be upper case functions for every
> concrete type? ... I'm just curious. I wouldn't actually use that feature.
Yes, it's just the constructor. In most cases you don't have to define them
manually, they are
On 8 July 2016 at 17:20, Tim Holy wrote:
> The string unification is already in julia-0.5.
>
I don't think I know what "string unification" means, but I guess part of
it is that Base.String will become ok to use again?
> There are functions called String(), Int(), and
The string unification is already in julia-0.5.
There are functions called String(), Int(), and Float64(). In some cases there
are lowercase variants, and these often "do more" (e.g., `float` will parse a
string and return an AbstractFloat). The uppercase versions are the minimalist
On Friday, 8 July 2016 16:01:25 UTC+2, Scott Jones wrote:
>
> We are looking forward to being able to use v0.5, with fast anonymous
> functions, cleaner array syntax, Gallium debugger and C++, and many many
> other improvements
>
Cleaner array syntax? Tell me more?
> (although the string
It used to be that [[1,2],[3,4]] would try to concatenate the two vectors
into [1,2,3,4], which was inconsistent with Vector{Int}[[1,2],[3,4]] (which
returns a vector of vectors).
That syntax was deprecated in v0.4.x, and in v0.5 now means the same thing
(and the same as in any other language
This is just me, but I prefer to wait a bit longer than to get mistakes
frozen into the language. One bit that I care about is the names of some
types and functions. For example, right now we have
- Base.String
- Base.ASCIIString
- Base.UTF8String
- Base.AbstractString
So, I want to use
Actually, the blog post from StaffJoy (
https://blog.staffjoy.com/retro-on-the-julia-programming-language-7655121ea341#.35atllel3)
never said that it turned out to be a mistake, in the conclusion they said:
> The Julia language helped to create Staffjoy and turn it into a business,
> and for
> For industry, it probably means something similar.
>
>
> I really hope people in industry won't act on this date, as it is not
> nearly firm enough to bet a business on. We already have people writing
> blog posts about how using Julia for their startup turned out to be a
> mistake; we really
>
> For industry, it probably means something similar.
I really hope people in industry won't act on this date, as it is not
nearly firm enough to bet a business on. We already have people writing
blog posts about how using Julia for their startup turned out to be a
mistake; we really don't
This information is hugely beneficial in science/mathematics, especially
for a PhD. It means that if you start a project in Julia now, although
there will be some bumps for when versions change, the project will likely
end after v1.0 is released (say 2 years?) and so your code should be stable
>
> I knew that.
>
The goal is 2017, if development community considers it to be ready.
I don't mean to be too glib, but I fail to see how any answer is
particularly actionable; it is certainly not binding.
On Thursday, July 7, 2016 at 10:14:24 AM UTC-4, Isaiah wrote:
>>
>> When it is ready.
OTOH many other people would prefer to wait a bit until certain design
decisions are hammered out in a satisfactory way. Stable & mature
software usually happens after spending a lot of time using and
developing unstable & immature software.
Incompatibilities are a pain, of course, but most
I knew that.
On Thursday, July 7, 2016 at 10:14:24 AM UTC-4, Isaiah wrote:
>
> When it is ready.
>
> On Thu, Jul 7, 2016 at 10:07 AM, Hisham Assi > wrote:
>
>> I really like Julia (I am using it for my publications & thesis), but I
>> noticed that the versions are not
I knew that.
On Thursday, July 7, 2016 at 10:14:24 AM UTC-4, Isaiah wrote:
>
> When it is ready.
>
> On Thu, Jul 7, 2016 at 10:07 AM, Hisham Assi > wrote:
>
>> I really like Julia (I am using it for my publications & thesis), but I
>> noticed that the versions are not
When it is ready.
On Thu, Jul 7, 2016 at 10:07 AM, Hisham Assi wrote:
> I really like Julia (I am using it for my publications & thesis), but I
> noticed that the versions are not really backward compatible. I am still ok
> with that, but many other people are waiting
I really like Julia (I am using it for my publications & thesis), but I
noticed that the versions are not really backward compatible. I am still ok
with that, but many other people are waiting for the mature, stable
version (1.0) to start using Julia. So, when Julia v1.0 will be released?
16 matches
Mail list logo