# Public Numba Dev Meeting, Tuesday October 13 2020

**URL:** <https://numba.discourse.group/t/public-numba-dev-meeting-tuesday-october-13-2020/253>\
**Category:** Announcements\
**Created:** [October 9, 2020, 3:22pm UTC](https://numba.discourse.group/t/public-numba-dev-meeting-tuesday-october-13-2020/253 "2020-10-09T15:22:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sklam](https://yyz2.discourse-cdn.com/free1/user_avatar/numba.discourse.group/sklam/32/9_2.png) [@sklam](https://numba.discourse.group/u/sklam)\
**Post date:** [October 9, 2020, 5:11pm UTC](https://numba.discourse.group/t/public-numba-dev-meeting-tuesday-october-13-2020/253/2 "2020-10-09T17:11:49Z")

</div>

Adding context to the “Type Annotation discussion”, the Numba devs continue to have some concerns about the idea of adding type annotations everywhere, and we are probably not as familiar with type annotations as some of our community members. So, I am inviting community members to help answer our questions and concerns about type annotations; especially:

- Type annotations can affect readability… long lines because of complex types.
- How to annotate NumPy arrays? Related to discussion in [https://github.com/numba/numba/pull/5609#pullrequestreview-492006847](https://github.com/numba/numba/pull/5609#pullrequestreview-492006847).
- Can we redirect the effort to annotate llvmlite first? Static type checks may have more immediate benefits in llvmlite.

---

_[View the full topic](https://numba.discourse.group/t/public-numba-dev-meeting-tuesday-october-13-2020/253)._