where's neither? renaming a confusing thing to a synonym doesn't achieve anything
How about using `tacit` instead of `implied` for Scala 3's new "implicit" syntax?
-
-
-
The third answer was meant to be a joke, but is effectively that. ;) But the reasoning is that the implicits system has changed considerably in Scala 3, and while it's an evolution, the concept is sufficiently different to warrant different names. I don't have strong feelings.
- Show replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Can we just use implicit again
-
Wouldn’t that be the portmanteau of implied and tacit?
- Show replies
New conversation -
-
-
«canonical»
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
or maybe surprise
End of conversation
New conversation -
-
why introduce a new keyword when we can just say `with this super abstract val`?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
More seriously I think implied is better; if you think of writing Scala as a conversation with the compiler, tacit doesn't seem right, since you specified which parameters to use, just not at the callsite
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.