Skip to content

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented Jan 8, 2024

  • Show strings with escaping, rather than trying to output the text unmodified.
  • Show symbols with the same formatting as Strings
  • Avoid accidentally defining a broken Core.show method for NamedTuple

@vtjnash vtjnash requested a review from JeffBezanson January 8, 2024 02:10
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
@vtjnash vtjnash force-pushed the jn/static-show-strings branch from 406ffa4 to 33e8cfe Compare January 8, 2024 14:04
@vtjnash vtjnash merged commit bd3eab6 into master Jan 9, 2024
@vtjnash vtjnash deleted the jn/static-show-strings branch January 9, 2024 00:57
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 23, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 23, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 23, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 23, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 27, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 27, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 29, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 29, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request May 30, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple
@KristofferC KristofferC added backport 1.10 Change should be backported to the 1.10 release backport 1.11 Change should be backported to release-1.11 labels Jun 5, 2025
KristofferC pushed a commit that referenced this pull request Jun 5, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple

(cherry picked from commit bd3eab6)
KristofferC pushed a commit that referenced this pull request Jun 5, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple

(cherry picked from commit bd3eab6)
KristofferC pushed a commit that referenced this pull request Jun 5, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple

(cherry picked from commit bd3eab6)
KristofferC pushed a commit that referenced this pull request Jun 5, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple

(cherry picked from commit bd3eab6)
kpamnany added a commit to RelationalAI/julia that referenced this pull request Jun 5, 2025
* static-show: improve accuracy of some printings (JuliaLang#52799)

- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple

* Make more types jl_static_show unambiguously (JuliaLang#58512)

Makes more types survive `jl_static_show` unambiguously:
- Symbols
- Symbols printed in the `:var"foo"` form use raw string escaping,
fixing `:var"a\b"`, `:var"a\\"`, `:var"$a"`, etc.
  - Symbols that require parens use parens (`:(=)`, ...)
- Signed integers: Except for `Int`, signed integers print like
`Int8(1)`.
- Floats: floats are printed in a naive but reversible (TODO: double
check) way. `Inf(16|32|)` and `NaN(16|32|)` are printed, and
`Float16`/`Float32` print the type (`Float32(1.5)`). `Float64`s are
printed with a trailing `.0` if it is necessary to disambiguate from
`Int`.

Fixes JuliaLang#52677,
JuliaLang#58484 (comment),
JuliaLang#58484 (comment),
and the specific case mentioned in JuliaLang#58484. Improves the situation for
round-trip (inexhaustive list):
- Non-canonical NaNs
- BFloat16
- User-defined primitive types. This one is tricky, because they can
have a size different from any type we have literals for.

* Use `julia__gnu_h2f_ieee` instead of `julia_half_to_float`

`julia_half_to_float` came in with an LLVM version upgrade after
v1.10.

---------

Co-authored-by: Jameson Nash <[email protected]>
Co-authored-by: Sam Schweigel <[email protected]>
KristofferC pushed a commit that referenced this pull request Jun 5, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple

(cherry picked from commit bd3eab6)
@KristofferC KristofferC mentioned this pull request Jun 25, 2025
71 tasks
@KristofferC KristofferC removed the backport 1.11 Change should be backported to release-1.11 label Jun 25, 2025
KristofferC pushed a commit that referenced this pull request Jul 3, 2025
- Show strings with escaping, rather than trying to output the text
unmodified.
- Show symbols with the same formatting as Strings
- Avoid accidentally defining a broken Core.show method for NamedTuple

(cherry picked from commit bd3eab6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 1.10 Change should be backported to the 1.10 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants