Fork me on GitHub

suppose you do not have a fixed (literal) path for things like setval, transform, etc. So, you have something like (transform [ATOM (apply keypath ks)] inc db). Does the 'This macro will do inline compilation and caching of the path.' still apply in this sort of situation? If not, is it still comparable in performance to update-in?


@jsa-aerial since ks is not static, you pay the cost of the apply and the keypath expansion on every invocation


not sure how it will compare to update-in but there will be a noticeable performance hit