# How can we maintain easy generics in the face of demand for a “safe” language?

**URL:** <https://discourse.julialang.org/t/how-can-we-maintain-easy-generics-in-the-face-of-demand-for-a-safe-language/109734>\
**Category:** Internals & Design\
**Created:** [February 5, 2024, 2:11pm UTC](https://discourse.julialang.org/t/how-can-we-maintain-easy-generics-in-the-face-of-demand-for-a-safe-language/109734 "2024-02-05T14:11:46Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [February 6, 2024, 7:19pm UTC](https://discourse.julialang.org/t/how-can-we-maintain-easy-generics-in-the-face-of-demand-for-a-safe-language/109734/18 "2024-02-06T19:19:41Z")

</div>

> [@Benny](#):
>
> Annotating a return type usually ends up as a `convert` step

Ah, right, I forgot that return type annotations are `convert` statements, not type checks, making them much less useful.

---

_[View the full topic](https://discourse.julialang.org/t/how-can-we-maintain-easy-generics-in-the-face-of-demand-for-a-safe-language/109734)._
