4,368 karma · joined December 2, 2012
Reach me at keno@juliacomputing.com
julia> 55555555555555555555
55555555555555555555
julia> typeof(55555555555555555555)
Int128
julia> typeof(5555555555555555555555555555555555555555)
BigInt (constructor with 7 methods)This issue was also reported at https://github.com/JuliaLang/julia/issues/5561
Julia's type system is very similar to Rust's. Julia has composite types, type unions and parametric dependent types. It is certainly designed with technical computing in mind, but that does not at all limit its ability to do general purpose programming and in fact can help significantly in high load situations. I personally have done more general purpose programming in Julia than I have done technical computing (and in fact, it's focus on technical computing was one of the least important reasons when I decided to become one of the Julia core developers). You have a good point that the ability to do easy technical computing certainly will influence the initial audience, but, I think, as the language matures, this will shift towards a more general audience.
If you're interested you can see the code for that completer here: https://github.com/loladiro/REPLCompletions.jl/blob/master/s...
Regarding types, all expressions are of type Expr or Symbol (there's a few other things that can be in the AST, but that's mostly it). What kind of expression it is is determined by the head field. There as some discussion about making the Expr type parametric on its head field so you can dispatch on that, but nothing in that direction recently.
It actually is more so than you might imagine. If you have julia installed try `julia --lisp` ;).
You can call Python from Julia now: https://github.com/stevengj/PyCall.jl
And there is also an effort underway to get iPython notebook integration (we met with Fernando Perez when he was in Boston to receive his award from the FSF and spent an afternoon hacking to get to this https://github.com/JuliaLang/julia-ipython - it's still in the very early stages of development though)
Disclaimer: I'm one of the core devs.
baremodule MyWay
ref(x::AbstractArray, i::Int) = Base.ref(x,i+1)
ref(args...) = Base.ref(args...)
end
is not that far away (I'm oversimplifying a little, but not much).
However, please don't do this as it breaks coherence within the community. I found 1-based indexes annoying at first, but have grown quite fond of them since.