Rafael Schouten

Yeah there is no difference. It must be the code path in Proj.jl missing some dispatch

Did you try looking at a profile? E.g. ProfileView.jl? It will show allocs and instability in yellow and red

I mean a sampling profiler like ProfileView.jl. Thats the best tool for this job because it will instantly show where the allocations are coming from. Just run that code a...

But... the profile will show if its type instability (boxing) causing allocation, or just regular allocation, red or yellow in the profile. (Likely red given dynamic dispatch warning). It also...

> I can't see this allocation or any instability in ProfileView from my end If there is nothing in the profile that suggests there isn't actually a problem. Time of...

Yes, totally breaking. It can be bumped with your other breaking PR.

The reason to switch is to unify the ecosystem. I would like it if `ArchGDAL.funcname` `LibGeos.funcname` `GeometryBasics.funcname` were as much as possible all the same when they do the same...

Oh yes exactly! I didn't mean to change the libgeos_api.jl file at all. I should have been clearer. I meant just the camelCase used outside of that file. Like `delaunayTriangulation`.

Doing this for MultiPoint and coordSeq methods is a huge task that I cant include in this PR. This package needs a rewrite of the internals with the aim of...

The eval is maybe less of a win due to readability, true. One good point to it is it forces you to be explicit about any differences between objects. In...