I'd suppose so, but asking just in case... does

copy { }

make another instance of the class on each

set

or

transform

called, or does it somehow aggregate the changes and make one copy in the end?

right now it creates a new copy each time

Oh.. I thought I understood from your video that it was better than kopykat in that sense... but nice to hear there's plans for it, thanks!

it’s better because it doesn’t copy to a mutable variable and then back again, it only creates one copy