Skip to content

Deprecate 'Clash.Prelude.DataFlow' #1490

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

Merged
merged 1 commit into from
Aug 26, 2020
Merged

Conversation

martijnbastiaan
Copy link
Member

@martijnbastiaan martijnbastiaan commented Aug 25, 2020

Current API makes it impossible to use for designs on multiple domains.
We should probably design something closer to cchalmers's circuit as
defined over at github.com/cchalmers/circuit-notation.

Deprecating due to namespace clashes for users designing dataflow
libraries that are better suited for real world designs.

edit: clash-protocols is now live!

Current API makes it impossible to use for designs on multiple domains.
We should probably design something closer to cchalmers's circuit as
defined over at github.com/cchalmers/circuit-notation.

Deprecating due to namespace clashes for users designing dataflow
libraries that are better suited for real world designs.
@@ -18,7 +18,7 @@ Self-synchronizing circuits based on data-flow principles.
{-# OPTIONS_GHC -fplugin GHC.TypeLits.Normalise #-}
{-# OPTIONS_HADDOCK show-extensions #-}

module Clash.Prelude.DataFlow
module Clash.Prelude.DataFlow {-# DEPRECATED "Module will be removed in future versions of clash-prelude." #-}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May or may not be the time for this, but I feel like we should commit to some fixed offset between deprecating something and removing it. The reason being

  • users would know how quickly they need to change their code before it breaks
  • we could better ensure deprecated code isn't removed too quickly / slowly

Thoughts?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Ideally we should point users to some alternative.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Guess I'll work a bit harder on martijn-circuits this weekend :-)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well now that you know a circuit is a symmetric monoidal category, what's stopping you? 😉

@martijnbastiaan martijnbastiaan merged commit 65a6255 into master Aug 26, 2020
@martijnbastiaan martijnbastiaan deleted the deprecate-dataflow branch August 26, 2020 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants