JuliaInterop / JuliaInterop/MathLink.jl

Handling of BigFloats/BigInts

Open
#25 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
146
Forks
34
PR merge metrics
No merged PRs in 30d

Description

Currently arbitrary precision values are represented by WReal and WInteger types, which are basically string representations. Should we automatically convert these to BigFloat/BigInts? The main downside is the additional overhead of parsing, and the potentially lossy binary/decimal conversion in the case of WReal.

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

The issue names no files or tests; start by locating the WReal and WInteger definitions and their uses. Evaluate conversion to BigFloat and BigInt against parsing overhead and possible WReal precision loss. Done requires a decided representation strategy and a defined implementation scope.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.