You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket replaces #325 from 2017. Goals: omit completed tasks, omit less-likely todos, make it easier to see the big picture & see where things stand.
Note that all the
t:replJLine 3 upgrade (scala/scala#8036)
tickets that we opened during the 2.13.3 cycle now live at
t:replJLine 3 upgrade (scala/scala#8036)
The prioritization here is based on part on the Twitter poll I did, as well as many years of discussions within the team and among the community.
Perhaps this could happen in Scala 3; I don't know. Certainly not happening in Scala 2: too much work, too disruptive.
I would encourage people to instead consider porting Ammonite features to the stock REPL, or to turn Ammonite into a wrapper or client of the stock REPL, to avoid code duplication.
This ticket replaces #325 from 2017. Goals: omit completed tasks, omit less-likely todos, make it easier to see the big picture & see where things stand.
Note that all the t:replJLine 3 upgrade (scala/scala#8036)
tickets that we opened during the 2.13.3 cycle now live at
t:repl
JLine 3 upgrade (scala/scala#8036)
The prioritization here is based on part on the Twitter poll I did, as well as many years of discussions within the team and among the community.
Modest goals
More ambitious
These remain possibilities for Scala 2, but would need discussion/planning. It would make the most sense to land it in Scala 3 first, then backport.
Shelved waiting for JLine fix
Out of scope
:require
featureThe text was updated successfully, but these errors were encountered: