Skip to content
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

Expose invalidate API and stop invalidating everything by default #413

Closed
jackkoenig opened this issue Dec 14, 2016 · 4 comments
Closed

Comments

@jackkoenig
Copy link
Contributor

It is safer to error when things are left unconnected. For use cases where various things are expected not to be connected, the user can explicitly invalidate Chisel values (not types).

@jackkoenig jackkoenig added this to the 3.0.0 milestone Dec 14, 2016
@ucbjrl
Copy link
Contributor

ucbjrl commented Dec 15, 2016

I've started a Google Doc for the Invalidate API. Please comment or edit that document. Once we've reached an internal consensus, we'll publish the content for public comment.

@colinschmidt
Copy link
Contributor

Presumably this wont affect code that doesn't import chisel3._

@jackkoenig
Copy link
Contributor Author

This will not affect the compatibility wrapper. It is intended to be improved safety for users of chisel3._

@ucbjrl
Copy link
Contributor

ucbjrl commented Nov 8, 2017

Fixed by #645

@ucbjrl ucbjrl closed this as completed Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants