Dotnet fsi broken on inputs that take more than 1 line
See original GitHub issuePlease provide a succinct description of the issue.
dotnet fsi breaks because it cannot read multiline expressions
Provide the steps required to reproduce the problem:
1 run dotnet fsi 2 insert any expr taking more than 1 line in console 3 reach the bottom of console 4 the interpreter goes crazy
7.0.2xx sdk:
issue does not exist in 7.0.1** sdk:
workaround is to revert back to 7.0.1
sudo apt-get install dotnet-sdk-7.0=7.0.104-1
Issue Analytics
- State:
- Created 6 months ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
dotnet fsi startup overhead surprisingly high · Issue #12636
On Windows I'm consistently seeing just above 1s for Measure-Command { dotnet fsi .\unit.fsx } . Quite a lot less than your Linux...
Read more >App.config and F# Interactive not working
While FSI dynamically generates code for your input, using the fsi.exe.config will work just fine. I created this file: <configuration> < ...
Read more >F# Interactive (dotnet) Reference
Learn how F# Interactive (dotnet fsi) is used to run F# code interactively at the console or to execute F# scripts.
Read more >F# Command Line Interactive Repl - linux
Rather than typing directly into a REPL, I recommend creating an F# script file ... Under openSUSE Leap 15.3 the command is dotnet...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I also experienced this on macOS.
The following update to console.fs to the function seems to resolve the issue on my Mac.