Explore JDK Vector API

Open
#215 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
backend-api-design

Research direction

Read JEP 338 first to understand the Vector API and its Java 16 status. Then inspect the uom-demos project and the existing Valhalla demos for the intended experimental entry points. Done means recording whether a Vector API experiment belongs in the API, implementations, or demos, and defining a concrete follow-up.

Written by the indexing model from the issue text.

Description

deferred design enhancement jdk

The JEP 338: Vector API first incubating in Java 16 sounds interesting.
Whether it may influence the API or (similar to Range, MixedQuantity, etc.) mostly implementations remains to be seen, but we should keep an eye on it and potentially experiment with it in uom-demos for Java 16 or similar to the Valhalla demos that are very early stage and experimental.

Dominant language
Java
Stars
195
Forks
41
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from unitsofmeasurement/unit-api

All issues in unitsofmeasurement/unit-api

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.