Skip to content

Conversation

@c42f
Copy link
Member

@c42f c42f commented Nov 22, 2022

jl_strtod_c can return "underflow" even for valid cases such as 5e-324 where the source string is parsed to an exact Float64 representation.

So we can't rely on jl_strtod_c to detect "invalid" underflow. Rather, only warn when underflowing to zero which is probably a programming mistake.

jl_strtod_c can return "underflow" even for valid cases such as `5e-324`
where the source string is parsed to an exact Float64 representation.

So we can't rely on jl_strtod_c to detect "invalid" underflow. Rather,
only warn when underflowing to zero which is probably a programming
mistake.
@c42f c42f merged commit b2b2441 into main Nov 23, 2022
@c42f c42f deleted the c42f/refine-underflow-warnings branch November 23, 2022 00:52
c42f added a commit to JuliaLang/julia that referenced this pull request Oct 17, 2025
…x.jl#154)

jl_strtod_c can return "underflow" even for valid cases such as `5e-324`
where the source string is parsed to an exact Float64 representation.

So we can't rely on jl_strtod_c to detect "invalid" underflow. Rather,
only warn when underflowing to zero which is probably a programming
mistake.
topolarity pushed a commit to JuliaLang/julia that referenced this pull request Nov 14, 2025
…x.jl#154)

jl_strtod_c can return "underflow" even for valid cases such as `5e-324`
where the source string is parsed to an exact Float64 representation.

So we can't rely on jl_strtod_c to detect "invalid" underflow. Rather,
only warn when underflowing to zero which is probably a programming
mistake.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant