Claire Foster

> We could also use https://github.com/c42f/FastClosures.jl, which I believe does the hack I described above, but is a registered, maintained(?) package Semi-maintained - I rather dislike that package and I...

Actually I didn't look at the details of your macro. All I meant to say is if there's another more predictable way to do this it might be preferable to...

@andyferris sorry about the mess on this branch, there were some crossed wires with a rebase! I tried to fix it up - hope it looks good to you now?

The CI errors here seem to be the issue in https://github.com/JuliaLang/julia/issues/7669 I think you need ```julia @eval hdf5_type_id(::Type{Float16})=H5T_FLOAT16 ```

JuliaSyntax.jl would probably offer a good way to do this — it initially parses the file into a `ParseStream` data structure which contains a vector of tokens and a vector...

Yes, the fact that the crash happens during a call to `require()` was concerning. Perhaps this indicates that `Base.require` itself is not threadsafe, because it appears to use plain `Base.Condition`,...

I didn't look into the detail here, but would adding custom rules make this more or less consistent? I wouldn't want to add rules which are convenient but inconsistent with...

The algebraic perspective taken in this package is that a `Rotation{N}` is a linear map from ℝᴺ→ℝᴺ (and therefore a N*N `AbstractMatrix`). So in this sense all rotation subtypes abstractly...

Another way to look at this algebraic problem would be to introduce a new function `rotate` distinct from `Base.*` which can take rotation parameterizations, such that `rotate(r, v)` rotates vector...

> One way to improve this i.m.o. would be to rename UnitQuaternion to something like QuatRotation. That way it's clear that quaternions are involved somewhere This is the main problem...