"Unbounded type variable" definition may need clarification
- Dominant language
- Java
- Stars
- 240
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Description
I'm not trying to be pedantic, but the term "unbounded type variable" shows up in the spec. Strictly speaking it is nonsensical since type variables have one or more bounds.
I _assume_ it means something like, simply, `T`. Does that mean that `T extends Object` is also supposed to be considered an "unbounded type variable" (I assume yes)? There are probably other edge cases I'm not thinking about right now.
Contributor guide
Research direction
Locate the "unbounded type variable" term in the CDI specification and read its surrounding definition and examples. Compare the treatment of a bare T with T extends Object and identify any other relevant edge cases. Done means the specification explicitly defines the term and resolves whether these forms are included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100