[GH-ISSUE #1167] Add type hints for all the class, functions in tinytorch #4335

Closed
opened 2026-04-19 12:20:28 -05:00 by GiteaMirror · 7 comments
Owner

Originally created by @harishb00 on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1167

Originally assigned to: @harishb00 on GitHub.

  • Ensure type hints are added for all classes and functions in the codebase.
  • Type hints help catch edge cases early and improve code readability and maintainability.
  • Without them, issues are only discovered after failing test cases, which slows down debugging and learning.
  • This will also benefit the students working on assignments, as type hints provide guidance and reduce ambiguity.

Additional context:
I am currently completing the assignments by removing the provided solutions using a script and solving them independently.

Originally created by @harishb00 on GitHub (Feb 11, 2026). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1167 Originally assigned to: @harishb00 on GitHub. * Ensure type hints are added for all classes and functions in the codebase. * Type hints help catch edge cases early and improve code readability and maintainability. * Without them, issues are only discovered after failing test cases, which slows down debugging and learning. * This will also benefit the students working on assignments, as type hints provide guidance and reduce ambiguity. Additional context: I am currently completing the assignments by removing the provided solutions using a script and solving them independently.
GiteaMirror added the type: improvementarea: tinytorch labels 2026-04-19 12:20:28 -05:00
Author
Owner

@harishb00 commented on GitHub (Feb 11, 2026):

Hi @profvjreddi , I would like to work on this issue. Can you please assign it to me?

<!-- gh-comment-id:3881944062 --> @harishb00 commented on GitHub (Feb 11, 2026): Hi @profvjreddi , I would like to work on this issue. Can you please assign it to me?
Author
Owner

@profvjreddi commented on GitHub (Feb 11, 2026):

Thanks so much @harishb00 -- I really appreciate you offering to help 🙏

<!-- gh-comment-id:3887839437 --> @profvjreddi commented on GitHub (Feb 11, 2026): Thanks so much @harishb00 -- I really appreciate you offering to help 🙏
Author
Owner

@profvjreddi commented on GitHub (Feb 19, 2026):

Hi @harishb00, really appreciate your contributions, from the type hints proposal here to the contribution guidelines fix and the cloning performance investigation. You're thinking about the health of the project itself, which is great.

We're having a TinyTorch community meetup on Tuesday, March 3rd at 9am. Would you be up for sharing a few minutes about your experience? What got you interested, what improvements you'd like to see, anything you'd like to discuss.

As one of our active contributors, we'd like to send you a small thank you too. Check Discord for more details!

<!-- gh-comment-id:3929785853 --> @profvjreddi commented on GitHub (Feb 19, 2026): Hi @harishb00, really appreciate your contributions, from the type hints proposal here to the contribution guidelines fix and the cloning performance investigation. You're thinking about the health of the project itself, which is great. We're having a TinyTorch community meetup on **Tuesday, March 3rd at 9am**. Would you be up for sharing a few minutes about your experience? What got you interested, what improvements you'd like to see, anything you'd like to discuss. As one of our active contributors, we'd like to send you a small thank you too. Check Discord for more details!
Author
Owner

@harishb00 commented on GitHub (Feb 20, 2026):

Thank you so much professor for the acknowledgement. I would love to be part of it. May I know the timezone? Need to check if I have any conflicts with other meetings. I am in IST. BTW, could you please share the discord link? I couldn't find it in the repo page.

Just noticed that my name is there in the contributors list. So happy. Thanks for recognizing even a small contribution like suggestions. I really appreciate that. Though there's a typo. It should be 'harishb00' rather it is mentioned as 'harishb00a'. I would like to raise a PR for that this week. So, I will have the satisfaction of actually making a commit than suggestions. 😁

<!-- gh-comment-id:3931383033 --> @harishb00 commented on GitHub (Feb 20, 2026): Thank you so much professor for the acknowledgement. I would love to be part of it. May I know the timezone? Need to check if I have any conflicts with other meetings. I am in IST. BTW, could you please share the discord link? I couldn't find it in the repo page. Just noticed that my name is there in the contributors list. So happy. Thanks for recognizing even a small contribution like suggestions. I really appreciate that. Though there's a typo. It should be 'harishb00' rather it is mentioned as 'harishb00a'. I would like to raise a PR for that this week. So, I will have the satisfaction of actually making a commit than suggestions. 😁
Author
Owner

@imuday984 commented on GitHub (Feb 21, 2026):

@harishb00 and I synced up on PR #1186. They are handling the type hints for 01_tensor and 02_activations

<!-- gh-comment-id:3938533627 --> @imuday984 commented on GitHub (Feb 21, 2026): @harishb00 and I synced up on PR #1186. They are handling the type hints for 01_tensor and 02_activations
Author
Owner

@imuday984 commented on GitHub (Feb 21, 2026):

I will pick up the work starting from 03_layers and 04_losses

<!-- gh-comment-id:3938535054 --> @imuday984 commented on GitHub (Feb 21, 2026): I will pick up the work starting from 03_layers and 04_losses
Author
Owner

@profvjreddi commented on GitHub (Feb 24, 2026):

Hi @harishb00,

Thanks for your interest in the TinyTorch community meetup on Tuesday, March 3rd at 9am. To get you set up as a speaker and share logistics, we need a few details from you.

Please:

  1. Reply to: karijanapareddi@gmail.com
    CC: vj@eecs.harvard.edu and andreamattia.garavagno@santannapisa.it

  2. Use the email address you want us to use for Zoom registration and for promoting you to panelist so you can speak on the call (it's a webinar-style meeting).

  3. Slide We'd love it if you could share a slide or two about your experience, you can add them here—there's a template to follow:
    https://docs.google.com/presentation/d/1h0bQZJVtmXYuO4jgakE3x3xGt0e8fNsvW7QfWK1_5D4/edit?slide=id.g3cac3cc65ae_0_19#slide=id.g3cac3cc65ae_0_19

We'll send logistical details (Zoom link, agenda, etc.) to your registered email.

Looking forward to having you on the call.

<!-- gh-comment-id:3952970231 --> @profvjreddi commented on GitHub (Feb 24, 2026): Hi @harishb00, Thanks for your interest in the TinyTorch community meetup on **Tuesday, March 3rd at 9am**. To get you set up as a speaker and share logistics, we need a few details from you. **Please:** 1. **Reply to:** **karijanapareddi@gmail.com** **CC:** vj@eecs.harvard.edu and andreamattia.garavagno@santannapisa.it 2. **Use the email address** you want us to use for Zoom registration and for promoting you to **panelist** so you can speak on the call (it's a webinar-style meeting). 3. **Slide** We'd love it if you could share a slide or two about your experience, you can add them here—there's a template to follow: https://docs.google.com/presentation/d/1h0bQZJVtmXYuO4jgakE3x3xGt0e8fNsvW7QfWK1_5D4/edit?slide=id.g3cac3cc65ae_0_19#slide=id.g3cac3cc65ae_0_19 We'll send logistical details (Zoom link, agenda, etc.) to your registered email. Looking forward to having you on the call.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#4335