From 5a3da67bb23d6fa0491127263240623dccebc04c Mon Sep 17 00:00:00 2001 From: Sairahcaz Date: Tue, 17 Jan 2023 08:55:31 +0100 Subject: [PATCH] doc update --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2784d8d..9373345 100644 --- a/README.md +++ b/README.md @@ -105,7 +105,7 @@ $myClass = new class() } ``` -So when calling `$myClass->processSomethingHeavy1(SomeModel::find(1))` the variable `$relation` will always have the same value as in `$myClass->processSomethingHeavy1(SomeModel::find(2))` as long as they have the same `foo_relation_id`. In spaties packge you would lose performance here, cause the ***containing method*** parameter ($someModel) has changed... Note that `processSomethingHeavy3` would also loose performance, even though the `foo_relation_id` would be the same, cause here also the changed **$someModel** would be used as the combination key. +So when calling `$myClass->processSomethingHeavy1(SomeModel::find(1))` the variable `$relation` will always have the same value as in `$myClass->processSomethingHeavy1(SomeModel::find(2))` as long as they have the same `foo_relation_id`. In some other memoization packges you would lose performance here, cause the ***containing method*** parameter ($someModel) has changed... Note that `processSomethingHeavy3` would also lose performance, even though the `foo_relation_id` would be the same, cause here also the changed **$someModel** would be used as the combination key and that model would have at least a different id. ## Enable/Disable