-
Notifications
You must be signed in to change notification settings - Fork 8
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
Remove CSignal
constructor
#67
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this change? why not:
Now
Bwd ()
andBwd (CSignal dom a)
are the same, and there's even less hope to makeBwd
injective again.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've given up the hope.. If we make an instance for
DSignal
(CDSignal
? 🥴) it will have the sameBwd
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To me a
Protocol
instance ofDSignal
does not make sense. I'd figure you either useDSignal
to build latency matched pipelines orProtocols
to build backpressure based pipelines, but you don't mix these.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO its existence would be motivated similar to
CSignal
: sometimes you just want to deal with a non-backpressure thing inCircuit
context.In any case, I just remembered the original motivation for dropping injectivity: all the protocols having a simple "acknowledge" on their
Bwd
would have to make newtypes, which turned out to be really annoying.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, you can mix backpressure and latency just fine; it's often a requirement for efficient pipelining without buffers. You'd have the contract that when
ready
deasserts, you can still transfer n more samples for a certain fixed n, after which the transfer stalls. For instance the Avalon Streaming interface supports this notion.I'm not acquainted enough with
clash-protocols
to really say how this relates here; I just noticed a dichotomy being constructed between latencies and backpressure that I think isn't there.