-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor all random functions to use applyreduce
#176
Comments
E.g. flatten, unwrap, reconstruct |
applyreduce
I think only function _flatten(f, target, geoms)
return applyreduce(f, vcat, target, geoms)
end (I think) |
I think even apply itself can just use applyreduce! - or they can all share a more generic/abstract function. I like the idea of having just one GeoInterface walker |
Yeah agreed, we should do that. What's the best approach though? I had considered having an The other alternative is to have an apply iterator, but that would be hard to thread. |
No description provided.
The text was updated successfully, but these errors were encountered: