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.
Both Windows and Unix have functions (
PurgeComm
andtcflush
) that clear out the underlying send and receive buffers without sending the data. This can be useful for call-and-response serial connections, where it makes sense to discard any existing data as invalid. There is a user demand for this addition (#56). This PR proposes a purge API and provides a Windows implementation.Both
PurgeComm
andtcflush
are single functions that accept a parameter indicating whether the input/receive queue, the output/send queue, or both queues should be flushed. This mimics that arrangement, adding apurge(&self, queue: Queue)
toSerialPort
andSerialDevice
. TheQueue
enum allows for input, output, or both.On Windows,
purge
is implemented using a single call toPurgeComm
. The Unix implementation should be similar, but I don't have a machine nearby to test with, so this is submitted as a draft PR for now with no Unix implementation.