-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Calling UDPSocket functions in REPL causes error. #14552
Comments
Didn't you fix this in #14325 ? |
That was where the errors were initially reported, but that PR only fixed show. |
What message has to be displayed for these functions? @tkelman |
I'm having trouble finding the last discussion on this with @JeffBezanson and @vtjnash but the conclusion was that the hierarchy of IO types probably needs some rearranging given this type doesn't support the stream interface. |
Is this the discussion? |
I'm bumping this - @abhijithanilkumar and @tkelman, was that the discussion? Can we add these in? Is this still a problem? |
Happened in a few other places as well. There's some rearrangement of the IO type hierarchy that's still an outstanding TODO here, things are grouped in a funny way where some subtypes of the same abstract type don't implement the same interface at all. But I don't think this needs to happen before 0.5. |
the main fix probably required here is that |
It seems the following UDPSocket functions are broken.
The text was updated successfully, but these errors were encountered: