You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
help?> Base.TwicePrecision
│ Warning
│
│ The following bindings may be internal; they may change or
│ be removed in future versions:
│
│ • Base.TwicePrecision
TwicePrecision{T}(hi::T, lo::T)
TwicePrecision{T}((num, denom))
A number with twice the precision of T, e.g., quad-precision if T =
Float64.
│ Warning
│
│ TwicePrecision is an internal type used to increase the
│ precision of floating-point ranges, and not intended for
│ external use. If you encounter them in real code, the most
│ likely explanation is that you are directly accessing the
│ fields of a range. Use the function interface instead,
│ step(r) rather than r.step
The text was updated successfully, but these errors were encountered:
At any, even minor, release of Julia. At any commit in Julia, really. Technically you're supposed to pin specific Julia versions in your Project.toml if you must trespass on the internals.
I'm not gonna update Project.toml on every Julia update. However it could be possible to trigger GitHub Actions to do the tests on Julia update. I'll leave this issue open until I (or someone) figure out how to do that.
putianyi889
changed the title
bug: the package uses the Julia-internal implementation detail TwicePrecision
warning: the package uses the Julia-internal implementation detail TwicePrecisionAug 23, 2024
EltypeExtensions.jl/src/EltypeExtensions.jl
Line 3 in 5414ec6
help?> Base.TwicePrecision │ Warning │ │ The following bindings may be internal; they may change or │ be removed in future versions: │ │ • Base.TwicePrecision TwicePrecision{T}(hi::T, lo::T) TwicePrecision{T}((num, denom)) A number with twice the precision of T, e.g., quad-precision if T = Float64. │ Warning │ │ TwicePrecision is an internal type used to increase the │ precision of floating-point ranges, and not intended for │ external use. If you encounter them in real code, the most │ likely explanation is that you are directly accessing the │ fields of a range. Use the function interface instead, │ step(r) rather than r.step
The text was updated successfully, but these errors were encountered: