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
Although I'd like to keep the async the default, @Xuanwo has a strong feeling about naming in #4626.
After a discussion offline, we agreed to follow Java's idiom to call the async version as AsyncOperator so that OperatorInputStream is a sync version.
I have a different opinion that InputStream is always sync because the async version should be something depends on ReactiveStream tech. And calling it BlockingOperatorInputStream is redundant. But I don't have such a strong feeling on switching BlockingOperator and Operator, while @Xuanwo's prefer to keep the name "consistent" so that "OperatorInputStream" associated to the blocking version "Operator".
The text was updated successfully, but these errors were encountered:
Although I'd like to keep the async the default, @Xuanwo has a strong feeling about naming in #4626.
After a discussion offline, we agreed to follow Java's idiom to call the async version as AsyncOperator so that
OperatorInputStream
is a sync version.I have a different opinion that InputStream is always sync because the async version should be something depends on ReactiveStream tech. And calling it
BlockingOperatorInputStream
is redundant. But I don't have such a strong feeling on switching BlockingOperator and Operator, while @Xuanwo's prefer to keep the name "consistent" so that "OperatorInputStream" associated to the blocking version "Operator".The text was updated successfully, but these errors were encountered: