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
Upon revisiting this section, I’m wondering whether it fits naturally within the context of function definitions for our interpreter. While I understand that closures are indeed related to functions, I find it challenging to explain how they tie into the interpreter itself, especially since the concept isn’t directly used to implement anything in this part. The exercises also feel somewhat disconnected from the main focus.
A possible alternative might be to move the closure discussion to the start of Chapter 9 (Protocols), where it is actively applied. Another option could be to place it at the end of Chapter 2 (Objects and Classes), where it introduces a different approach to implementing the object system. The downside to this would be that those chapters might become longer while this chapter becomes shorter.
To address the potential imbalance, one could consider moving the content about functions into the interpreter chapter, which might provide a more coherent (albeit longer) flow.
The text was updated successfully, but these errors were encountered:
sback
changed the title
/func - Section 8.3: Closures (2024-04-28)
/func - Moving Section 8.3: Closures ? (2024-04-28)
Oct 2, 2024
Upon revisiting this section, I’m wondering whether it fits naturally within the context of function definitions for our interpreter. While I understand that closures are indeed related to functions, I find it challenging to explain how they tie into the interpreter itself, especially since the concept isn’t directly used to implement anything in this part. The exercises also feel somewhat disconnected from the main focus.
A possible alternative might be to move the closure discussion to the start of Chapter 9 (Protocols), where it is actively applied. Another option could be to place it at the end of Chapter 2 (Objects and Classes), where it introduces a different approach to implementing the object system. The downside to this would be that those chapters might become longer while this chapter becomes shorter.
To address the potential imbalance, one could consider moving the content about functions into the interpreter chapter, which might provide a more coherent (albeit longer) flow.
The text was updated successfully, but these errors were encountered: