# Type instability with Type{T} selectors in keyword arguments

**URL:** <https://discourse.julialang.org/t/type-instability-with-type-t-selectors-in-keyword-arguments/129439>\
**Category:** General Usage\
**Created:** [May 29, 2025, 2:02pm UTC](https://discourse.julialang.org/t/type-instability-with-type-t-selectors-in-keyword-arguments/129439 "2025-05-29T14:02:47Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![marcsgil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marcsgil/32/33908_2.png) [@marcsgil](https://discourse.julialang.org/u/marcsgil)\
**Post date:** [May 29, 2025, 3:14pm UTC](https://discourse.julialang.org/t/type-instability-with-type-t-selectors-in-keyword-arguments/129439/5 "2025-05-29T15:14:28Z")

</div>

I see. In the setting that I’m imagining, the user will just set this keyword value as `CuArray` or some other GPU array type according to their hardware. Then this should be safe?

---

_[View the full topic](https://discourse.julialang.org/t/type-instability-with-type-t-selectors-in-keyword-arguments/129439)._