raboof commented on issue #1740: URL: https://github.com/apache/pekko/issues/1740#issuecomment-2615788639
Yes, I think you understood it correctly - this is further confirmed by the next sentence > Rather, it could be seen that APIs which expose those SPI types to end-users are leaking internal implementation details accidentally. I don't remember the history, but I think there were some other implementations that were marketing themselves as supporting Reactive Streams "more natively" because they were directly extending those classes, which doesn't really make sense. Perhaps we should make it a bit more direct, and replace those two lines with something like: > In other words, these classes are intended to be an internal detail of interoperable libraries. While some other libraries expose the SPI types directly to end users, for example by inheriting from them, you could say this leaks an internal implementation detail. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
