homedirectory

5 ms·

1. 1.▲
   by homedirectory 2y ago

   From the article: > I want it to be the case that this function only actually calls do-something-very-expensive once per unique value of x, even across separate invocations of dumb-example. My code memoizes results of function FIB _insid
2. 2.▲
   by homedirectory 2y ago

   You can achieve memoization of an expression inside a function without any global state and macros: (defun compute-hash (key hash f) "Get the value for KEY in HASH or compute it with F, enter into HASH and return."
3. 3.▲
   by homedirectory 2y ago

   Your fear of macros is natural, since they are not typical for a programming language. It is expected that a newcomer to Lisp is likely to have a hard time grasping macros. You should not be disregarding one of the most powerful features of
4. 4.▲
   by homedirectory 2y ago

   I also once thought that the magic underlying SETF has access to true L-values, and had also been surprised by it being macros under the hood. Here are my thoughts on the article: Firstly, there are errors in the definition of OUR-SETF macr
5. 5.▲
   by homedirectory 2y ago

   Thank you for sharing this demo. Amazing stuff! Inspired me to start working on improvements to the development environment of my team.
6. 6.▲
   by homedirectory 3y ago

   Thanks. This feature is described as optional for 3rd party apps and a claim is made that the information is not sent off the device. Assuming this is true, I take back my criticism about the policy being invasive.
7. 7.▲
   by homedirectory 3y ago

   See "Privacy and Security" section. > And it [Communication Safety] extends beyond Messages to include content sent and received in AirDrop, ..., and third‑party apps. This distorted Apple's vision of privacy is not news t