-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
=> operator does not work in place of Via #79
Comments
I'm not sure right now, but I guess, that the current definition of Unfortunately original Akka GraphDSL uses almost all scala-specific features in one place (implicit params, implicit type casting, custom operators with multiple overloads etc.). It's hard to create something remotely similar in any other language. |
I see. So there is no way to make it work with => operator? Maybe add a type hint somewhere? |
Yes. I usually try to keep public API method signatures with all types definitions set explicitly to avoid such mistakes as this one. |
Hi @vasily-kirichenko, does this work for you? (I know it is ugly...) And if I execute code like this
It throws exception...
Excuse me, do you know how to fix it? |
@ingted in your code you defined |
You may also want to take a look at the example of using Akkling graph API. |
I expect
Flow<ITweet, IUser, NotUsed>
here instead ofFlow<ITweet, ITweet, NotUsed>
.The text was updated successfully, but these errors were encountered: