Fix the infinite loop issue when WebSocket returns an error message in the example case. #3508
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When websocket.receive() encounters an error, it cannot be properly thrown, resulting in an infinite loop within AsyncStream, which negatively impacts performance.
Writing this way allows the error to be handled properly, avoiding the issue mentioned earlier.
socket.receive() is a throwing function.
In the case of SwiftUICaseStudies:
03-Effects-WebSocket.swift
The error throwing form
Message(socket.receive())
will be caught byResult<Success, Failure>
This will cause the AsyncStream to continuously unexpectedly throw errors indefinitely.
It would be better to handle the Success and Failure cases separately.