This was stranger than I thought, seem to depend on the order of
invocations to f. Issue filed:
https://github.com/JuliaLang/julia/issues/5577
On Monday, 27 January 2014 18:21:56 UTC+1, Stefan Karpinski wrote:
>
> That is weird and may be a dispatch bug. Perhaps an issue should be
> opened.
>
That is weird and may be a dispatch bug. Perhaps an issue should be opened.
On Sun, Jan 26, 2014 at 3:00 PM, Toivo Henningsson wrote:
> The type of a type would e.g. describe which values are legal as the
> second argument of isa.
> It turns out that Type almost works. If I do
>
> julia> f(::An
The type of a type would e.g. describe which values are legal as the second
argument of isa.
It turns out that Type almost works. If I do
julia> f(::Any)=false
f (generic function with 1 method)
julia> f(::Type)=true
f (generic function with 2 methods)
Then
julia> f(Int)
true
julia> f((Int,St
What do you mean by "the type of a type"?
I wanted recently to be able to write a type annotation that would cover
all the types of all the arguments to (exported) functions in Base. The
following currently works:
~~~
Types = Union(DataType,UnionType,TypeVar,TypeConstructor,())
AtomicType = Union
On Saturday, 25 January 2014 18:36:59 UTC+1, David Piepgrass wrote:
>
>
> 3. Julia has first class types, so types are values in the language. Tuple
>> types are written as a tuple of the types, which seems fairly
>> straight-forward. Your version, Tuple{Int,Int}, would require a new type
>> f
On Saturday, January 25, 2014 09:36:59 AM David Piepgrass wrote:
> > I think you misunderstand. Rounding up to 8 bits makes sense; not
> > allowing
>
> the user to define, say, a 23-bit type is what I question.
See BitArrays, which store logical values using a single bit. In the end
you're alwa
In theory, LLVM supports integer types of an arbitrary number of bits. But
in our experience oddball integer sizes that C doesn't use typically don't
work very well. This may improve over time and make it more reasonable to
have a user-defined 23-bit integer type. In principle, we could certainly
a
References for splicing vs splatting in the latest manual:
http://docs.julialang.org/en/latest/manual/style-guide/?highlight=splicing#don-t-overuse
http://docs.julialang.org/en/latest/stdlib/base/?highlight=splicing#Base.apply
Also, if Julia were to support 23 bits types, what would it mean? Shou
>> Some of these, such as the arrow key thing, sound like they might be better
>> as a github issue. I don't know what the expected behavior on windows is.
>The issue is process termination, but don't Shift+Arrow and Ctrl+Arrow work
>the same way on Windows and Linux nowadays? Not sure about the
You're right, I'm sorry for not numbering my thoughts or anything.
Some of these, such as the arrow key thing, sound like they might be better
> as a github issue. I don't know what the expected behavior on windows is.
>
The issue is process termination, but don't Shift+Arrow and Ctrl+Arrow wor
Regarding the `x::Int = 5` behavior, I just had a conversation with Jeff
and Stefan yesterday where they helped me understand better how that works.
My understanding certainly still may be flawed or incomplete, in which case
I welcome corrections.
The syntax `x::Int` can mean a few different thing
I may miss parts of your email. It is more challenging to respond when you
dump many unrelated questions into the same email. (It would be easier if
you organized or numbered the different issues/comments, or reduced the
number of comments/email)
Some of these, such as the arrow key thing, sound l
I started learning Julia today so I have some random comments/questions.
Firstly, Julia looks great. It is only the second dynamic language that I
have ever seriously felt like using. The first dynamic language I liked was
Ruby, until I came to appreciate the shortcomings of a dynamic language i
13 matches
Mail list logo
