On 26 January 2017 at 01:40, phil@highoctane.be <phil@highoctane.be> wrote:

Yeah, I get you 100%.

I wanted to be able to cache or not and have this transparent.

Memoization in its current form in Pharo is not like I would like to have it.

As for the repeating block, I was asking to how you would avoid repeating in the given code structure.

You asking me rewrite it for your example?
unless i missing something (not)obvious here, it can look like this:��

getIssueCreateMeta

"Retrieves the metadata for all types of issues. Fields are expanded"

^ self cache at: ��#issueCreateMeta ifAbsentPut: [��self getIssueCreateMetaWithExpandKeys: true��]

��

Btw, it is a good question, what are the difference between caching and memoization, besides that google underlines 'memoization' word with thin red curly line while i typing? :)��

Best regards,
Igor Stasenko.