Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REPL: print to stdout instead of TTYTerminal to avoid over-specialization #37127

Merged
merged 2 commits into from
Aug 25, 2020

Conversation

KristofferC
Copy link
Sponsor Member

@KristofferC KristofferC commented Aug 20, 2020

Fixes #37020. Implements the suggestion in #37094 (comment).

Now the IO that the REPL passes down to the display system has the same type as the one used in non-interactive use. The precompilation statements collected in the REPL are therefore also valid for the non-interactive use-case.

@JeffBezanson
Copy link
Sponsor Member

Could we be more thorough and do this inside outstream? Is there any reason to do IO on a TextTerminal instead of its underlying stream?

@KristofferC
Copy link
Sponsor Member Author

I thought about that too and convinced myself it didn't work. But it totally does so changed to that...

@KristofferC KristofferC merged commit 3d04d15 into master Aug 25, 2020
@KristofferC KristofferC deleted the kc/repl_stdout branch August 25, 2020 10:29
simeonschaub pushed a commit to simeonschaub/julia that referenced this pull request Aug 29, 2020
…tion (JuliaLang#37127)

* REPL: print to stdout instead of TTYTerminal to avoid over specialization
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.

error printing latency regression
2 participants