We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
xxx.submodules
Issue by mithro Tuesday Dec 18, 2018 at 00:37 GMT Originally opened as m-labs/nmigen#10
A huge number of issues in the old migen are caused by forgetting to assign something to xxx.submodules.
Is there any reason that we can't do something like this?
class Module: def __setattr__(self, k, v): if isinstance(v, Module): self.add_module(k, v) object.__setattr__(self, k, v)
The text was updated successfully, but these errors were encountered:
Comment by whitequark Tuesday Dec 18, 2018 at 00:38 GMT
You do not inherit from Module in nMigen.
Sorry, something went wrong.
Comment by whitequark Tuesday Dec 18, 2018 at 00:52 GMT
And incidentally the reason you don't is this.
Comment by whitequark Tuesday Dec 18, 2018 at 00:57 GMT
Also, see #3--in nMigen forgetting to add a submodule will be a hard error, though I'm not yet sure exactly how this will be detected.
No branches or pull requests
Issue by mithro
Tuesday Dec 18, 2018 at 00:37 GMT
Originally opened as m-labs/nmigen#10
A huge number of issues in the old migen are caused by forgetting to assign something to
xxx.submodules
.Is there any reason that we can't do something like this?
The text was updated successfully, but these errors were encountered: