-
Notifications
You must be signed in to change notification settings - Fork 358
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
Move connection flags to Connection
static const member
#2517
Conversation
…rameter to Connection static const member
bd3b50e
to
710008a
Compare
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.
Very nice :-)
I have added some inline comments to further improve the encapsulation of the flags.
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.
…model() parameter to Connection static const member
@clinssen: I know you are busy, but still: any news on this?! |
Thank you for the reviews! The new changes should address all of the comments raised. |
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.
@clinssen This looks so much nicer now that it inspired me to some ideas to make it even tidier :).
@clinssen: I have just sent you clinssen#6 to fix the problem with the failing assertions. Locally, I still see some tests failing and I can look into this hopefully tomorrow. |
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 second most of @heplesser's comments and have added some additional ones.
Static node flags
@jougs, @heplesser: thanks very much for your input! The latest commits should address all of your comments exactly as you proposed them, so there are no unresolved conversations remaining. Could you give it another look (or seal of approval)? Cheers! |
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.
Only some minor remarks left.
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.
Thanks!
@heplesser, @med-ayssar: could one of you please have a quick look? I think this is good to go. Thanks! |
We meanwhile have a positive review by @med-ayssar
A
Connection
knows best about its own required connection flags. These flags are therefore moved from theModelsModule
, where each individual model is registered with the kernel through aregister_connection_model()
call, to theConnection
class and its children (such as theclopath_synapse
) as a new memberconst static RegisterConnectionModelFlags flags
. Clopath and Urbanczik models initialize them using their own flags, OR-ed with the default flags in the base class.@jougs: should we keep the non-const
operator|
on our customEnum
type, or ditch it?If you are happy with how this looks, I will make the same changes for the secondary connection flags.