Skip to main content

9. Data Type Casting (Gerunds & Infinitives)

Objective: Learn how to "cast" an Execution Command (Verb) into a Data Variable (Noun) so it can be passed as a payload into an object slot. Master the logic of "Forward Pointers" vs. "Concrete Data."

Part 1: Standard Library Upgrade (Pre-Compiled Blocks)​

Instructor Note: Memorize these as complete, unbreakable blocks of code.

A. The Corporate API​

The BlockThe LogicExecution
Wrap upTo finish or conclude a task or meeting."Let's wrap up this code review before lunch."
Factor inTo include a specific detail in your calculations or plans."We need to factor in the deployment time."

B. The Casual API​

The BlockThe LogicExecution
Look forward toTo feel excited about something in the future."I look forward to visiting my family."
Get around toTo finally do something you have been delaying."I finally got around to fixing my ThinkStation P3."

Part 2: The Core Logic (Why 'To' vs. '-ing')​

If a slot in your sentence strictly requires a Noun, you cannot just drop a raw V1 Verb into it. You must "Type Cast" it. How do you know which cast to use? It depends entirely on the semantic logic of the Main Verb running the sentence.

1. The Infinitive (To + V1): The Forward Pointer

  • The Logic: We use to when the second action is unrealized, hypothetical, or in the future. You are pointing forward to a task that hasn't happened yet.
  • Execution: "I want to code today." (The coding hasn't happened; it is a future desire).

2. The Gerund (V4 / -ing): The Concrete Data Block

  • The Logic: We use -ing when the second action is realized, based on experience, ongoing, or finished. You are looking at the action as a concrete, existing block of data.
  • Execution: "I enjoy coding." (Coding is a real, experienced process that you like).

Part 3: The Dependency Routing Tables​

The Main Verb dictates the cast. Use the logic below to compile the correct data type.

Group A: The Forward Pointers (Forces To + V1)​

These verbs structure or point to a future state.

  • Want / Need / Hope: "I need to deploy the code."
  • Plan / Decide / Expect: "We decided to roll back the update."
  • Promise / Agree / Offer: "He promised to fix the bug."
  • Manage / Afford: "I managed to finish the script."

Group B: The Concrete Processes (Forces V4 / -ing)​

These verbs deal with actions that are already happening, are based on experience, or are being terminated.

  • Enjoy / Mind / Dislike: "I enjoy working as a freelancer."
  • Finish / Quit / Give up: "I finished writing the documentation."
  • Avoid / Postpone / Delay: "We should avoid pushing to production on Fridays."
  • Suggest / Recommend: "I suggest testing the database first."

Group C: The Routing Preposition Rule (Strict Override)​

If you use ANY preposition (in, on, at, for, about, of, without), the very next action MUST be cast as a Gerund. There are zero exceptions.

  • Execution: "I am thinking about learning React."
  • Execution: "I use pink salt for making my oats taste better."

Part 4: System Warnings (Overloaded Functions)​

Instructor Note: Watch out for these highly common compiler errors.

1. The Overloaded Memory Functions (Stop / Remember): These functions completely change their output depending on which data type you pass them.

  • Stop / Remember + -ing (Look Backward): "I remember buying this MacBook Pro in 2019." (Looking at a past data log). "I stopped eating sugar." (Terminating an ongoing process).
  • Stop / Remember + to + V1 (Look Forward): "Please remember to buy a new laptop." (Looking at a future task). "I stopped to eat." (I paused my current process in order to eat).

2. The "Look Forward To" Bug: In the API block "look forward to", the word "to" is a Preposition, not an infinitive marker. Therefore, it triggers Group C and strictly requires a Gerund.

  • Fatal Error: "I look forward to work with you."
  • Clean Code: "I look forward to working with you."

Part 5: Interactive Code Refactoring (25 Questions)​

Instructions for the student: Refactor the sentences by choosing the correct Type Cast. Use the Forward Pointer vs. Concrete Data logic to guide you. Write your clean code directly below each corrupted sentence.

1. (Corporate): "We need (factor in) the new API rate limits before we launch." (Hint: 'Need' points to a future state)

2. (Casual): "I usually avoid (walk) near the main road in Brookefield because of the traffic." (Hint: 'Avoid' pushes away a concrete process)

3. (Corporate): "The client suggested (wrap up) the project by next Friday." (Hint: 'Suggest' proposes an ongoing concept)

4. (Casual - Bug Fix): "I am looking forward to see my sister this weekend."

5. (Corporate - Purpose): "I opened the terminal for checking the error logs." (Hint: When explaining 'Why' you did something, use the Forward Pointer)

6. (Casual): "I finally got around to (teach) my sister the new English grammar rules." (Hint: 'To' is a preposition here in this API block)

7. (Corporate): "We cannot risk (push) the broken Python code to production." (Hint: 'Risk' deals with an experienced/realized danger)

8. (Corporate - Memory Overload): "Please remember (save) your progress on the Lenovo ThinkStation before it reboots." (Hint: Are you looking backward at a log, or forward at a task?)

9. (Casual - Memory Overload): "I remember (buy) this MacBook Pro back in 2019; it was a great day."

10. (Corporate): "Are you interested in (learn) more about React frameworks?" (Hint: Apply the Group C Preposition Rule)

11. (Casual - Bug Fix): "I suggest to whip up some spicy oats for dinner."

12. (Corporate): "Before (deploy) the application, we must run the unit tests."

13. (Casual): "I promise (help) you plan the trip for your friend."

14. (Corporate): "I look forward to (factor in) your great feedback in the next sprint."

15. (Corporate - Bug Fix): "We stopped to write the code because the server crashed." (Hint: Did they pause in order to write it, or did they terminate the writing process?)

16. (Casual): "I use pink salt (make) my pre-workout drink taste better." (Hint: Explaining the 'Why' / Purpose)

17. (Corporate): "They decided (roll back) the database update."

18. (Casual): "(Cook) paneer is one of my favorite things to do on the weekend." (Hint: Cast the verb into a Subject Noun. Treat it as a concrete concept)

19. (Corporate): "The freelance contract requires me (sign off on) the final wireframes."

20. (Casual): "I haven't got around to (catch up with) my university friends yet."

21. (Corporate): "Thank you for (escalate) this issue so quickly."

22. (Casual): "I am planning (upgrade) my 2019 MacBook Pro soon."

23. (Corporate): "Let's hold off on (wrap up) the meeting until the CEO arrives."

24. (Casual - Bug Fix): "I went to the gym for doing some upper body strength training."

25. (Corporate/Casual - Full Refactor): "I enjoy to work as a freelancer because I don't mind to work late hours, but I am looking forward to take a vacation soon." (Hint: Fix all 3 Type Casting errors using the logic tables)

Click here to view the System Output (Answer Key)

1. * Clean Code: "We need to factor in the new API rate limits before we launch."

  • Logic: Need is a Forward Pointer (hypothetical future state).

2. * Clean Code: "I usually avoid walking near the main road in Brookefield because of the traffic."

  • Logic: Avoid pushes away a concrete, experienced process.

3. * Clean Code: "The client suggested wrapping up the project by next Friday."

  • Logic: Suggest deals with an ongoing concept/concrete data block.

4. * Clean Code: "I am looking forward to seeing my sister this weekend."

  • Logic: "To" is a preposition here, triggering the strict Preposition Override (Group C).

5. * Clean Code: "I opened the terminal to check the error logs."

  • Logic: Explaining the purpose/why of an action requires the Infinitive Forward Pointer.

6. * Clean Code: "I finally got around to teaching my sister the new English grammar rules."

  • Logic: "To" is a preposition in the API block get around to.

7. * Clean Code: "We cannot risk pushing the broken Python code to production."

  • Logic: Risk deals with an experienced/realized danger (Concrete Process).

8. * Clean Code: "Please remember to save your progress on the Lenovo ThinkStation before it reboots."

  • Logic: Looking forward to a future task.

9. * Clean Code: "I remember buying this MacBook Pro back in 2019; it was a great day."

  • Logic: Looking backward at an existing memory log.

10. * Clean Code: "Are you interested in learning more about React frameworks?"

  • Logic: "In" is a preposition (Group C Override).

11. * Clean Code: "I suggest whipping up some spicy oats for dinner."

  • Logic: Suggest always takes a Gerund (Concrete concept).

12. * Clean Code: "Before deploying the application, we must run the unit tests."

  • Logic: "Before" is a preposition (Group C Override).

13. * Clean Code: "I promise to help you plan the trip for your friend."

  • Logic: Promise points to a future, unexecuted state.

14. * Clean Code: "I look forward to factoring in your great feedback in the next sprint."

  • Logic: Preposition override for "look forward to".

15. * Clean Code: "We stopped writing the code because the server crashed."

  • Logic: They terminated an active, ongoing process. They didn't pause in order to write it.

16. * Clean Code: "I use pink salt to make my pre-workout drink taste better."

  • Logic: Explaining the purpose/why of using the salt.

17. * Clean Code: "They decided to roll back the database update."

  • Logic: Decide structures a future state.

18. * Clean Code: "Cooking paneer is one of my favorite things to do on the weekend."

  • Logic: Cast into a Subject Noun. It is treated as a concrete concept.

19. * Clean Code: "The freelance contract requires me to sign off on the final wireframes."

  • Logic: Require points to an unexecuted future obligation.

20. * Clean Code: "I haven't got around to catching up with my university friends yet."

  • Logic: Preposition override for "get around to".

21. * Clean Code: "Thank you for escalating this issue so quickly."

  • Logic: "For" is a preposition (Group C Override).

22. * Clean Code: "I am planning to upgrade my 2019 MacBook Pro soon."

  • Logic: Plan points to a future state.

23. * Clean Code: "Let's hold off on wrapping up the meeting until the CEO arrives."

  • Logic: "On" is a preposition in the API block hold off on.

24. * Clean Code: "I went to the gym to do some upper body strength training."

  • Logic: Explaining the purpose (Forward Pointer). Never use "for doing" to explain why you went somewhere.

25. * Clean Code: "I enjoy working as a freelancer because I don't mind working late hours, but I am looking forward to taking a vacation soon."

  • Logic: Enjoy and Mind deal with experienced, concrete processes. Look forward to triggers the Preposition Override.