Alex Arslan

We can just use GitHub's archive functionality.

cc @davidanthoff

Perhaps I'm misunderstanding what you mean, but if actual `convert` methods should be defined, e.g. `Float64(::DateTime)` becomes meaningful, that should happen in Base. Packages shouldn't make those kinds of extensions...

```shell git checkout float_time git fetch origin git rebase origin/master # Fix any merge conflicts manually git push origin/float_time ```

I freely admit to not know much about this stuff, but it seems weird to me for `==` and `isequal` to behave differently.

This is one of my concerns with automatic lifting. I'm hoping that with the planned `Nullable` revamp in Julia 1.0, `map` and `broadcast` will not lift. IMO it doesn't make...

Yes, a general idea would be to have two separate null-like concepts, one like `NA` in DataArrays (modeled after its namesake in R and behaves like a scalar) and one...

No, it will be a `Union` as it is now, but there are planned optimizations for `Union`s in 1.0.

I hope you don't mind but I converted your list to a checklist for easier tracking of what's been done.

If I did remove it, it was probably before OrderedCollections was split out from DataStructures, or something like that. I don't really remember but I agree this is bad. Since...