G-Node / G-Node/nix-java

Variant/Value: unsigned type support

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

Nobody has claimed this yet.

Dominant language
Java
Stars
0
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Currently we only support signed integer types, because Java traditionally only supported unsigned data types. This changed with Java 8 which added support for unsigned interpretation of data represented by int/long. See [Java Datatypes][https://docs.oracle.com/javase/tutorial/java/nutsandbolts/datatypes.html). In Java Variant/Value bindings we only allow getting the signed types because we call get() with a signed argument and if the underlying type is unsigned that will fail in the datatype check. I wonder if it not best to augment Variant to better support the bindings by adding a function that allows copying the raw data to a buffer of specified size or something.

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.

Research direction

Start at the Java Variant/Value binding calls that use get() and compare them with the underlying Variant datatype checks. Define completion as a supported way to retrieve unsigned int and long representations without signed-type rejection, with coverage for the Java 8 unsigned cases described in the issue.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.