Design discussion
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
Direzione di ricerca
Inizia da src/NestedNumbers.jl ed examples/usage_demo.jl, quindi esamina le draft PRs collegati e il contesto di Reactant e Discourse. L’issue cerca il parere critico della community sul nome del package, sulla gerarchia dei tipi e sull’approccio complessivo, invece di specificare una modifica circoscritta; per considerarla completata sarebbe necessario concordare una direzione o una proposta concreta di follow-up.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
We have some number types in the Julia ecosystem that are "a bit special". The one's I have encountered most often are quantities (numbers with units), opaque/traced/symbolic numbers (value not accessible at all) and numbers that are "remote", i.e. that live on a separate compute-node/device/system (value accessible only with substantial latency).
Making such numbers subtypes of Real and Integer is tricky, dispatch wise, but also semantically not ideal - one might argue that a traced number with a real value is not actually a real number itself - I can operate on it, but I can't compare values and make a branching decision based on it (at least not during tracing). Likewise, a real number with a unit is clearly not a real number itself. On the other hand, user code often needs to restrict numerical type, both for semtantic and dispatch reasons - a function that will behave wrong for complex values should ideally not use Number at the argument type.
Also see https://github.com/EnzymeAD/Reactant.jl/issues/1570 and https://discourse.julialang.org/t/flexunits-jl-0-3-0-support-for-unitful-like-inference/134903/38 for context.
NestedNumbers is an attempt to create a bridge here - a super-lightweight package that user code can depend on and use for dispatch, while only minimal changes are required for unit packages or packages that use traced numbers like Reactant.
See the NestedNumbers demo, which requires these draft PRs:
- https://github.com/JuliaPhysics/Unitful.jl/pull/837
- https://github.com/Deduction42/FlexUnits.jl/pull/52
- https://github.com/JuliaPhysics/DynamicQuantities.jl/pull/198
- https://github.com/EnzymeAD/Reactant.jl/pull/2434
The final approach should ideally involve UnitsBase as well.
(Note that Reactant doesn't seem to work with unitful numbers in general yet, so the demo doesn't show a combination of both. )
The basic approach is this: NestedNumbers defines
- Abstract types like
OpaqueNumber{T}RemoteNumber{T}QuantityNumber{T}that packages that define number types can subtype. - Union typedefs like
AReal,AInteger,AComplex,ABoolandQReal,QInteger,QComplex,QBoolfor user/downstream code to dispatch on.
It's all in the single short source file.
Everyone involved/interested is more than welcome to comment and critique here, propose radical changes (feel free to open PRs), etc. NestedNumbers is not registered yet on purpose, everything is up for change including the package name. This is an attempt to see if this kind of approach can work and would be acceptable, and it's meant to involve the whole community.
- Lingua principale
- Julia
- Stelle
- 2
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
CliMA/ClimaArtifacts#184 ·
-
In-place Vern7 stiffness estimate uses mismatched stage valuesForse già presa @devmotion l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
SciML/OrdinaryDiffEq.jl#4778 ·
I maintainer di solito rispondono entro 1 giorno
-
`pick_batchsize` spends ~1 µs constructing `BatchSizeSettings{B}(N)` with a run-time `B`Forse già presa @devmotion l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
JuliaDiff/ReverseDiff.jl#318 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100