Want to build a tool to document papercuts. I think there's a lot of value to be had in documenting the small speedbumps you experience, at the time you experience them. Think the optimization path from "good" to "excellent" often lies in figuring out where the papercuts are.
Ah yeah, I suspected as much. Would be really nice if the lifetime could be extended to cover the enclosing closure or smth tho.
I still haven't gotten this to work right (because Cow for custom structs is another fun rabbit hole
).
-
-
Not sure what your current struggle with Cow is but would be happy to discuss this in person
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.