Java Float Audit for PTC-Lisp

Copy Markdown View Source

Warning: This file is auto-generated by mix ptc.gen_docs from priv/java_compat_audit.exs. Manual edits will be overwritten. Edit priv/java_compat_audit.exs instead.

Curated LLM-compatibility target for java.lang.Float.

See also: Function Reference | Namespace Coverage | Clojure Core Audit | Clojure String Audit | Clojure Set Audit | Clojure Walk Audit | Java Math Audit | Java Boolean Audit | Java Double Audit | Java Integer Audit | Java Long Audit | Java String Audit | Java System Audit | Java LocalDate Audit | Java Instant Audit | Java Duration Audit | Java Period Audit | Java Date Audit

Summary

Coverage excludes not_relevant entries: supported / (supported + candidate + not_classified).

StatusCount
Supported1
Candidate3
Not Relevant1
Not Classified0
Relevant Target4
Coverage1/4 (25.0%)
Total5

Details

VarStatusDescriptionNotes
Float/isInfinite🔲 candidateReturn true if value is infiniteCommon guard around parsed floating data.
Float/isNaN🔲 candidateReturn true if value is NaNCommon guard around parsed floating data.
Float/parseFloat✅ supportedParse string to floatBUG GAP-J01: currently aliases parse-double, returns nil on invalid input, and rejects surrounding whitespace that Java accepts. PTC-Lisp uses one floating type.
Float/valueOf🔲 candidateParse or box a float valueparse-double covers string parsing; boxing is not relevant.
floatValue❌ not_relevantUnbox a Float objectPTC-Lisp has one floating type, not boxed Java numbers.