Types defined even when an error happens

[nalimilan]

This is what I just got when writing bool instead of Bool:

julia> type DataValue
           value
           isna::bool
        end
ERROR: type: DataValue: in type definition, expected Type{T<:Top}, got Function

julia> type DataValue
           value
           isna::Bool
        end
ERROR: invalid redefinition of constant DataValue

So it looks like after an incorrect definition you end up with an incomplete type or something...

(Yes, newcomers are terrible testers, every stupid thing will be tried! ;-)

[StefanKarpinski]

(Yes, newcomers are terrible testers, every stupid thing will be tried! ;-)

This is exactly what makes them the best testers! The half-initialized state for both types and modules is unfortunate and would be great to avoid.

[ivarne]

The half-initialized state is at least something that can be fixed without fixing the more complex issue of recompiling the code that depends on assumed constants (like type declarations and method definitions).

[pygy]

I still get this using v0.3.0-prerelease+1658.

julia> type Fuu() end
ERROR: syntax: invalid type signature

julia> type Fuu end
ERROR: invalid redefinition of constant Fuu

[ivarne]

@pygy What platform are you on. I do have either of the problems on OSX master as of yesterday?

[pygy]

Indeed, it's fixed in HEAD. My build was about 1 month old, but more recent than the 893033c commit that fixed the issue. I guess it got merged in between.