You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just thinking out loud -
either the entire conversion could happen on a single data in which case it might be fine for Evaluate to take in the datetime, but there could be also Transactions of different dates that we are dealing with in which case it be along with the Transaction
The text was updated successfully, but these errors were encountered:
@rahulpnath I think you are expecting the operations happening over a long period of time (says, few days or week). One possible, but less preferred way of doing this would be to run the money calculator for that period of time. In that case, the solution would be to Evaluate the wallet as soon as you operate. However, that, as I mentioned, would be less preferred. Because everything will be lost if the system crashes. So, the more accurate of doing it would be to store the wallet into some permanent storage so that it can be brought into memory when needed. In that case, the DateTime stamp with each transaction will make sense. Along with that, the wallet also needs to be serializable. I am just trying to think a strong use-case for this feature, as this will require quite a large amount of change in the way I currently handle any mathematical operation, or transaction if you like.
Just thinking out loud -
either the entire conversion could happen on a single data in which case it might be fine for Evaluate to take in the datetime, but there could be also Transactions of different dates that we are dealing with in which case it be along with the Transaction
The text was updated successfully, but these errors were encountered: