Persist history of flowR REPL sessions

[Ellpeck]

persistory

[codecov]

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (d69018e) 71.34% compared to head (e890221) 71.34%.
Report is 2 commits behind head on main.

Files	Patch %	Lines
src/cli/repl/core.ts	72.72%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #641      +/-   ##
==========================================
- Coverage   71.34%   71.34%   -0.01%     
==========================================
  Files         217      217              
  Lines        7005     7015      +10     
  Branches     1085     1087       +2     
==========================================
+ Hits         4998     5005       +7     
- Misses       1720     1722       +2     
- Partials      287      288       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[EagleoutIce]

wuhuuu!

[EagleoutIce]

Theoretically, we have a problem when someone runs multiple repls at the same time which overwrite each other but hey... we live only once!

[Ellpeck]

Theoretically, we have a problem when someone runs multiple repls at the same time which overwrite each other but hey... we live only once!

Thoretically, we could keep a stream to the history file open while repl is active and store the history into the file that way. Then, we could just print a warning and skip storing the history for any sessions that are started on top of the original one.

[EagleoutIce]

Yes, or we could keep a History-Tree but I think the current handling is sufficient as the most frequent use case will be the restart of the repl after compilation

[EagleoutIce]

This pull request is included in v1.4.2 (see Release v1.4.2 (Dropping xmlparsedata, Benchmark Re-Runs, and Repl Fixes)).