Timeline for Universal memoization decorator
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 5, 2015 at 2:33 | history | edited | Veedrac | CC BY-SA 3.0 |
deleted 1 character in body
|
| Jan 24, 2015 at 20:08 | comment | added | Veedrac | @rroszkowiak It's not an inherent thing, it's just that sans the use of globals, having immutable inputs requires a pure function. | |
| Jan 24, 2015 at 19:49 | comment | added | rroszkowiak | Right, but my point is why would one enforce the use of only hashable objects as function arguments (which needs to happen to use frozenset)? I mean do you consider using unhashable objects as function arguments as not "pure"? | |
| Jan 24, 2015 at 19:43 | comment | added | Veedrac |
If I understand the question, it's because {'x': some_unhashable_object} isn't hashable.
|
|
| Jan 24, 2015 at 19:31 | comment | added | rroszkowiak | Thank you! My way of building of arg_dict was totally screwed compared to yours. And, actually, whereas I realize the mutable type as a default argument should not happen, why passing the list as a function argument would be against purity in this case? | |
| Jan 24, 2015 at 17:06 | history | answered | Veedrac | CC BY-SA 3.0 |