Repository navigation
Plugin Operators and static typing #7298
Replies: 2 comments 3 replies
|
Hi Dries. Plugin operators are not currently supported with static typing I'm still on the fence about whether to support it, since plugin operators / factories add methods to standard entities ( Also, I have found that a plugin operator can almost always be re-implemented as a plugin function and used with existing operators. A function is easier to implement and more flexible than an operator or factory I'm happy to help you work through any specific use case you have in mind |
|
Hi Ben, thanks for the reply. Might I suggest adding this as a note or warning to the migration docs? From what I understand enabling static typing breaks code that uses plugins. On the matter of operator vs function: when you say that an operator can be re-implemented as a function: do you mean that its always possible to create a function that takes a channel-typed argument and returns an output channel? In that case the only real difference in this case is that chaining using I would be happy to read your input on this one! Thanks, |
Uh oh!
There was an error while loading. Please reload this page.
I wanted to experiment with the new static typing and making some plugin operators compatible with it. The current plugin system documentation recommends using
DataflowWriteChannelandDataflowReadChannelas the types for the operator return values and parameters. However, as far as I understand, enabling static typing requires the use of other classes (e.g.ChannelImpl,ValueImpl, ...). What is the recommended way to write operators that are compatible with the static typing system?Thanks!
All reactions