Lewin Bormann

Hi Henning! Similarly to #18 or #19 this appears to be a question of whether `memoize` should be a silver bullet solution to all caching. At the moment the goal...

I will try to take a look soon. In the meantime, you're welcome to try it out yourself -- but I understand if it's not an option, the python code...

Sorry for forgetting so long about this - is this still an issue for you, or have you found a workaround?

Got it - I was asking in case you'd given up on this code and rolled something yourself :) I guess a quick fix is to attempt encoding anything but...

The reason it's done like that is #3 - the lock cannot be held while calling the original function, because it might again call the memoizer. So, either be racy...

Thanks, that sounds interesting! I'm not 100% sure how to integrate it though; the idea of using mpsc channels is nice but not trivially integrated with tokio (for that, using...

Having notify using Futures would obsolete this crate -- probably for the better :-) I have no idea about Windows, unfortunately, so I'm depending on contributors sending patches for that...

As I have stated in issues here before, while I'm open to feature requests, some of the feature requests sound like you are expecting too much from an automatic memoization...

Indeed! That would make writing a Rust generator a lot easier to write.

```rust use memoize::memoize; #[derive(Clone)] struct Struct {} #[derive(Clone)] struct Error {} #[memoize(SharedCache, Capacity: 1024)] fn my_function(arg: &'static str) -> Result { println!("{}", arg); Ok(Struct{}) } fn main() { let s...