UCSBarchlab/PyRTL

Documentation for memblocks has no max write ports

dkupsh opened this issue · 0 comments

On read the docs, it states:

max_write_ports (max_read_ports,) – limits the number of read and write ports each block can create; passing None to either indicates there is no limit

I think this is a typo because it doesn't have max_read_ports in the documentation and the type is wrong.

On Line 173 in memory it states:
:param max_read_ports, max_write_ports: limits the number of read and write ports each block can create; passing 'None' to either indicates there is no limit

Should it be copied to state:
:param int max_read_ports: limits the number of read ports each block can create; passing 'None' indicates there is no limit
:param int max_write_ports: limits the number of write ports each block can create; passing 'None' indicates there is no limit