David Widmann

> (perhaps related to #122 ?) Yes, the bracketing error seems to be a duplicate of #122.

BTW the general performance issues should have been fixed by https://github.com/JuliaStats/Distributions.jl/pull/1277.

I added print statements in https://github.com/JuliaStats/HypothesisTests.jl/blob/c2d4c3a29be325edc1594f4b4affa7b5d8f4afde/src/fisher.jl#L189-L190 and https://github.com/JuliaStats/HypothesisTests.jl/blob/c2d4c3a29be325edc1594f4b4affa7b5d8f4afde/src/fisher.jl#L196-L197 to show the bracketing intervals and the values of the objective function at these points. It seems the problem is that the...

A constructor won't prevent breakage of downstream dispatches on `UniformScaling`. If we consider this a valid example (maybe there are others, it was just the first thing that came to...

@willtebbutt I can definitely see your point. IMO it's an edge case and one could argue one way or the other. I don't think the use of `UniformScaling` is completely...

My experience with this in SciML is that currently the only proper way to solve this explicitly (i.e., without AutoPreallocation) is to have dedicated types and caches for in-place and...

The main problem is to guarantee that 1) you can actually mutate stuff and 2) that the element types are correct. In particular, 2) is quite tricky - e.g., what...

Where exactly? It's difficult to say without concrete example but in general I don't think it's a good idea to rewrite large parts with explicit loops since then you might...

> edit2: the only other reason to like the `x -> f -> lik` over `(x, f) -> lik` is that if you want to compute the likelihood for multiple...

I don't understand the changes in this PR, can you explain the motivation? The compat issues seem to be caused by ElasticPDMats/GaussianProcesses/WilliamsGPR. I don't remember the details but there was...