# Traits, Generics, and modern-day OO for Fortran

**URL:** <https://fortran-lang.discourse.group/t/traits-generics-and-modern-day-oo-for-fortran/8426>\
**Category:** Announcements\
**Created:** [August 2, 2024, 6:29pm UTC](https://fortran-lang.discourse.group/t/traits-generics-and-modern-day-oo-for-fortran/8426 "2024-08-02T18:29:32Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![FortranFan](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@FortranFan](https://fortran-lang.discourse.group/u/FortranFan)\
**Post date:** [August 3, 2024, 11:16pm UTC](https://fortran-lang.discourse.group/t/traits-generics-and-modern-day-oo-for-fortran/8426/14 "2024-08-03T23:16:47Z")

</div>

@kkifonidis , @certik ,

Great effort. However based on the immediate and long-term needs of the practitioners of Fortran, any proposal toward Traits, Generics, or whatever that is based on **type(T), …** should really be a non-starter, absolutely [dead on arrival](https://en.wikipedia.org/wiki/Dead_on_arrival#Colloquial_use) (DOA).

All the examples in the “Traits.pdf” have “type(T) …”

I would give a firm NO to this if I had a vote!

Please review this post recommending [**KIND, ATTRIBUTE, RANK, and TYPE aspects**](https://fortran-lang.discourse.group/t/kart-a-recommended-design-element-toward-generics-in-fortran/8431). as a fundamental building block toward any enhancement toward Generics.

Given all the work in Fortran starting with `ANSI FORTRAN 1966` through the current Fortran 2023 revision that has made use of TKR semantics and some ATTRIBUTE and what has been introduced with `INTERFACE` block, traits or generics based on “type(T)” is too limiting.

You can refine your proposal a lot better via an **entity block** idea.

---

_[View the full topic](https://fortran-lang.discourse.group/t/traits-generics-and-modern-day-oo-for-fortran/8426)._