On Thu, 28 May 2026 10:34:40 GMT, Emanuel Peter <[email protected]> wrote:
>> Paul choose not to sprinkle the Float16 instead of primitive type every >> where, and suggested to add a normative paragraph at the start of >> Float16Vector.java which mentions about Float16 being considered as >> primitive type >> https://github.com/jatin-bhateja/jdk/blob/fdb0e33c1933c6c12e42e7fabc827e93d5fd75a1/src/jdk.incubator.vector/share/classes/jdk/incubator/vector/Float16Vector.java#L65 > > @PaulSandoz I see. That's nasty and probably bound to lead to some confusion > down the line. But I understand why we you chose to do it. Indeed. It's a compromise, as is using `short` for scalar values. When `Float16` eventually transitions to a value type that behaves, for the most part like `short`, we can align more closely. Furthermore, after JEP 401 goes in it opens the door to preview `IntVector` etc, but `Float16Vector` has to remain incubating with `Float16` until the next Valhalla JEP previews. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/28002#discussion_r3318462973
