We had a semi-consensus on calling it scala-library-future, but the more I think about it, the more I think that the ambiguity with scala.concurrent.Future is bad news. It maybe isn't so bad on a screen, but when you say "scala library future" out loud, it's reallllly ambiguous.
For now I've named the repo "scala-library-next", but it can still be renamed, we aren't locked in until we actually publish the initial version.
Thoughts?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4