memoizer | Memoize your methods

"If I use memorizer future builder still runs at least two times (not forever), but get and set functions doesn't work and new values are not updated and are not notified to the widgets."

That is the expected behaviour:

Error: The server encountered an error processing the request. See server logs for more details

This issue comes into picture whenever there is any issue at WCF service. So see more details about the issue, you need to includeexceptiondetailInfaults attribute to true in servicedebug tag.

Instructions can't be reordered if they violate the sequential semantics of a program.

Simple example (assuming a=b=0):

You can use let fibo instead of const fibo. Then replace the fibo variable with a memoized version. By updating fibo the nested call will now refer to the memoized fibo function instead of the original.

The primary optimization you should use here is common subexpression elimination. Consider your first piece of code:

I have modified my proguard.conf to:

It might be a bit too early to say for sure but we might have solved it by removing the following two line from our config/initializers/i18n.rb

With the definition of a "pure function" being:

In computer programming, a pure function is a function that has the following properties:[1][2]

Its return value is the same for the same arguments (no variation with local static variables, non-local variables, mutable reference arguments or input streams from I/O devices). Its evaluation has no side effects (no mutation of local static variables, non-local variables, mutable reference arguments or I/O streams).

I think we can see that what you have is a pure function, if the same values are passed to the function, you will always get the same result; there is nothing in that method that would be affected by any external state beyond it –– that is unless the passed fun argument isn't pure, but that isn't an issue with your memoizer method itself.

EDIT Because the cache object is not a static variable, mutating it does not violate any of the rules of what makes a pure function pure. Definition of "side effects" as used by Wikipedia in the explanation above:

In computer science, an operation, function or expression is said to have a side effect if it modifies some state variable value(s) outside its local environment, that is to say has an observable effect besides returning a value (the main effect) to the invoker of the operation.

Beginning with JNA 5.x, the Structure class fields are identified with the @FieldOrder annotation. For the Timeval structure causing your problem, it's defined like this: